~/.octaverc overwrites OCTAVE_PATH!!

Rosen Diankov rdiankov at cs.cmu.edu
Sun Dec 21 14:38:52 CST 2008


Hi all,

I'm trying to append my own directory with octave files
(/usr/local/myoctavefiles) to the automatically set octave paths. At
first, I tried doing

export OCTAVE_PATH=/usr/local/myoctavefiles

but it didn't work since the auto-generated ~/.octaverc file (from
savepath) overwrites any added paths via the path function. Ie, the
~/.octaverc file looks like:

## Begin savepath auto-created section, do not edit
  path ('/usr/local/share/...',...)
## End savepath auto-created section

So the next obvious thing to do was to call
addpath('/usr/local/myoctavefiles') right after the '## End savepath
...', but this has a very dangerous side-effect. The problem is that
the next time the user calls 'savepath', it will put
/usr/local/myoctavefiles inside the auto-generated code. And even if I
remove my addpath or set OCTAVE_PATH to something different, my path
will remain added to the octave path!

So I propose a small savepath change that always puts
getenv('OCTAVE_PATH') inside the auto-generated code.
It would be great if this makes it into octave 3.0.4

thank you,
rosen diankov,


More information about the Help-octave mailing list