Pathdef.m

[John W. Eaton]

On  8-Feb-2006, Keith Goodman wrote:

| Would it make sense to add a pathdef.m file to store the Octave
| path?  It could be placed in a new directory ~/.octave which could also
| contain octaverc and octave_hist.
| 
| It is easy for each user to customize Octave as above. I was just
| wondering if it would be a good idea to make it the default behavior.
| 
| If each user can have a pathdef.m, then it makes sense to also have a
| system-wide pathdef.m.
| 
| I guess the first step would be to bring over addpath, rmpath, and
| savepath (changing the dafault save location to ~/.octave/pathdef.m)
| from octave-forge.
| 
| Or do you think it makes more sense to keep the path in octaverc?

What do you propose to put in pathdef.m (especially the system-wide
one) that can't already go in .octaverc?

How should addpath, rmpath, and savepath interact with Octave's
DEFAULT_LOADPATH and recursive directory searching?

jwe