Mail Archives: cygwin/2006/02/09/12:04:27
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//];
++++++++
I then add my own private octave functions to the directory tree under
~/.octave. I tested that adding a new m-file more than one level down does
make it available when octave is restarted, forcing the path to be
re-traversed.
Please realize that normally the LOADPATH is only recursed once, at the time
octave is loaded. If you put new functions out there, you need to force octave
to re-read the path. There may be other ways to do it, but the easiest is to
exit and restart.
This is unlikely to be a cygwin packaging issue. You will likely receive more
help at help AT octave DOT org.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -