[octave ] LOADPATH recurses only one level of subdirectories

2006-02-09 Thread Larrie Carr
In 2.1.72-1, the LOADPATH or DEFAULT_LOADPATH use of the "//" path ending only appears to recurse 1 subdirectory level. I've attach a test_recurse.m that shows how the "butter.m" file appears as the path is "lowered". According to the octave documentation, all subdirectories are supposed to be

[octave ] LOADPATH recurses only one level of subdirectories

2006-02-09 Thread Larrie Carr
Your attachments don't seem to be available, so I am not able to see the structure of your test. However, a test of my own indicates the functionality does work. What I do is create a file called .octaverc in my own home directory, with the contents LOADPATH=[LOADPATH,':~/.octave/

Re: [octave ] LOADPATH recurses only one level of subdirectories

2006-02-09 Thread Larrie Carr
| In short, octave-forge is non-functional as it uses multiple subdirectories. If that's true for everyone, then I'm surprised as I think you are the first to report it. Sorry about the tone - it's not functional for me, while everyone else is happy. I've tried a clean new cygwin installat

[octave ] LOADPATH recurses only one level of subdirectories (on network drives)

2006-02-10 Thread Larrie Carr
John W. Eaton wrote Probably the code you are looking for is the function do_subdir in liboctave/kpse.cc. This file contains a stripped-down version of the kpathsearch library. Most modifications were to remove TeX-specific stuff and to convert it to use std::string instead of plain C strings w

[octave ] LOADPATH recurses only one level of subdirectories (on network drives)

2006-02-11 Thread Larrie Carr
ave using a method that works on every other system except cygwin. Larrie. Larrie Carr wrote John W. Eaton wrote Probably the code you are looking for is the function do_subdir in liboctave/kpse.cc. This file contains a stripped-down version of the kpathsearch library. Most modifications were

Re: Problems after upgrading to 1.5.19-4

2006-03-08 Thread Larrie Carr
From: "Timothy King" Last night, I grabbed an additional package using setup.exe. It also downloaded and installed the latest cygwin1.dll (1.5.19-4) and core utilities. I had not updated since early January. While it was running the post-install script, I received serveral errors along the l

Re: Problems after upgrading to 1.5.19-4

2006-03-09 Thread Larrie Carr
From: "Dave Korn" wrote On 09 March 2006 05:45, Larrie Carr wrote: I had this problem a couple of months ago. My problem was caused by the setup.exe being very helpful and (at least for me) defaulting to always installing the latest version of anything you already had installed. An

Re: Problems after upgrading to 1.5.19-4

2006-03-09 Thread Larrie Carr
From: "Dave Korn" On 09 March 2006 18:22, Dave Korn wrote: ... one paragraph that needs a little clarification: On 09 March 2006 17:51, Larrie Carr wrote: But the latest is not always the best. For instance, octave could only be compiled with gcc 3.3.3 - but the latest in setu

Re: Problems after upgrading to 1.5.19-4

2006-03-09 Thread Larrie Carr
From: "Dave Korn" On 09 March 2006 19:37, Larrie Carr wrote: Sure I RTFM'ed and yes it says that. But I would argue that Keep does not exactly work the way that you say it does. So not using Keep does not indicate RTFM status. Well, since keep ABSOLUTELY DOES work EXACTLY