[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: addpath/rmpath and PKG_ADD/PKG_DEL
From: |
c. |
Subject: |
Re: addpath/rmpath and PKG_ADD/PKG_DEL |
Date: |
Tue, 25 Feb 2014 11:53:24 +0100 |
On 25 Feb 2014, at 11:17, Julien Bect <address@hidden> wrote:
> Yes, it is explained in the manual in the section that describes packages.
>
> But
>
> 1) there is no mention, in the section of the manual you're referring to, of
> the fact that this behaviour is automatically achieved by the functions
> addpath/rmpath (it is not obvious that "pkg load ..." implies a call to
> rmpath, for instance),
>
> 2) this appears to be in fact a general behaviour of addpath/rmpath, even
> outside the world of packages,
>
> 3) and there is no mention of this behaviour of addpath/rmpath if you type
> "help addpath" or "help rmpath".
>
> If you confirm that this is indeed the intended behaviour of addpath/rmpath,
> even outside packages, then I can prepare a patch for the documentation of
> these functions in libinterp/corefcn/load-path.cc.
the PKG_ADD file is sourced whenever the directory that contains it is added to
the path.
if you have mydir/PKG_ADD and you start Octave from within mydir, PKG_ADD will
be sourced at startup.
this is not handled by "pkg"
> @++
> Julien
c.