Re: Initialization of load_path at startup

[John Swensen]

On May 14, 2008, at 10:52 AM, Kim Hansen wrote:

> On Wed, May 14, 2008 at 2:02 PM, John Swensen  
> <address@hidden> wrote:
> > I am having a strange problem with the load_path while working on  
> > OctaveDE.
> > Below I have listed the results of the path() command just after  
> > startup.
> > I have been searching for how the load_path is initialized at  
> > startup and
> > cannot figure out how in the world that extra line is getting  
> > injected when
> > I start up octave_main from OctaveDE, and it is not happening when  
> > simply
> > running octave.
> >
> >
> > First 3 lines of output of path() command in Octave when executed  
> > from
> > Octave.app
> > .
> > /Applications/Octave.app/Contents/Resources/share/octave/site/m/ 
> > startup
> > /Applications/Octave.app/Contents/Resources/libexec/octave/3.0.1/ 
> > oct/i386-apple-darwin8.9.1
> >
> >
> > First 3 lines of output of path() command in Octave when running in
> > OctaveDE.app
> > .
> > ./Applications/Octave.app/Contents/Resources/share/octave/site/m
> > /Applications/Octave.app/Contents/Resources/share/octave/site/m/ 
> > startup
>
> I think this is the same bug as
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477556, and I also
> think I have found a solution, patch is attached.
>
> I am not really sure why we start with "." in the xpath variable, as
> "." always is in path, I have just tried to fix the bug without
> creating a new one.
>
> --
> Kim Hansen
> Vadgårdsvej 3, 2.tv
> 2860 Søborg
> Fastnet: 3956 2437 -- Mobil: 3091 2437
> <sys_path.patch>

Yes, I think that would fix it, although I found another solution.  As  
long as I start executing OctaveDE.app while in the directory / 
Applications/Octave.app/Contents/Resource then things work fine.  I  
don't quite get this, but since I change the directory after Octave  
starts up anyway, it is an acceptable solution for me (and I don't  
have to rebuild Octave.app).

John