[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Suggestion: startup.d subdirectory for use by octaverc
From: |
James R. Phillips |
Subject: |
Re: Suggestion: startup.d subdirectory for use by octaverc |
Date: |
Sun, 3 Jul 2005 20:47:39 -0700 (PDT) |
--- Paul Kienzle wrote:
> We already have this---through a PKG_ADD file in your package directory
> and all octave commands therein will be run. IIRC, PKG_DEL is run when
> the directory is removed from the path.
Hmm. No documentation that I can find within octave on this. Did find this
comment in list archives:
http://www.octave.org/octave-lists/archive/octave-maintainers.2002/msg00175.html
===========
There is also some new code for declaring commands at startup time.
Now when a directory is added to the LOAADPATH, Octave looks for a
file called PKG_ADD in the directory, and if it is present, reads and
executes commands from it.
===========
OK. But actually, what I had in mind was exactly the issue of adding a
directory to the LOADPATH, which is typically done in octaverc, and must be
done before PKG_ADD is of any assistance. Scripts to do this could be put in a
startup.d directory with octaverc. They could then be added or deleted from
the subdirectory as necessary, in concert with package addition or deletion,
and without requiring edits of octaverc.