Re: Pathdef.m

[Keith Goodman]

On 2/8/06, John W. Eaton <address@hidden> wrote:
> What do you propose to put in pathdef.m (especially the system-wide
> one) that can't already go in .octaverc?

Nothing new, just a different way of organizing. I think of octaverc
as a place to customize octave with convenience features. And in my
case it is a messy place. I think of pathdef as a place for an
auto-generated path---a clean place.

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

That's beyond me. But I use addpath all the time without any problems.