Message-ID: <20060209170412.2974.qmail@web51512.mail.yahoo.com>
Date: Thu, 9 Feb 2006 09:04:11 -0800 (PST)
From: "James R. Phillips" <antiskid56-cygwin AT yahoo DOT com>
Reply-To: antiskid56-cygwin AT yahoo DOT com
Subject: [octave ] LOADPATH recurses only one level of subdirectories
To: cygwin AT cygwin DOT com
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

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/