octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: addpath/rmpath and PKG_ADD/PKG_DEL


From: Julien Bect
Subject: Re: addpath/rmpath and PKG_ADD/PKG_DEL
Date: Tue, 25 Feb 2014 11:55:35 +0100
User-agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0

On 25/02/2014 11:53, c. wrote:
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"

Yes, this was precisely the point of the test script attached to my initial email.

Since you confirm that this is an intentional feature of addpath/rmpath, I will prepare a patch for their doc.

@++


reply via email to

[Prev in Thread] Current Thread [Next in Thread]