Re: gnuplot 4.5

[John W. Eaton]

On 11-Nov-2009, address@hidden wrote:

| You're right :
| 
| octave:1> [status,output] = system("which gnuplot")
| status = 0
| output = /usr/bin/gnuplot
| 
| Then I tried
| 
| octave:3> [status,output] = system("echo $PATH")
| 
| which yields
| 
| status = 0
| output = 
/usr/lib/octave/3.0.1/site/exec/x86_64-pc-linux-gnu:/usr/lib/octave/api-v32/site/exec/x86_64-pc-linux-gnu:/usr/lib/octave/site/exec/x86_64-pc-linux-gnu:/usr/lib/octave/3.0.1/exec/x86_64-pc-linux-gnu:/usr/bin:$PATH
| 
| Where $PATH is the variable set in my .bashrc. Why does octave add
| /usr/bin to my path? That is what is causing the "wrong" gnuplot to be
| called.

I don't remember precisely, but I'm guessing now that the reason was
so that the mkoctfile and octave-bug script could be found even if the
directory where they (and Octave) are installed is not in your PATH
when you start Octave.  The directory /usr/bin is actually $bindir,
which may be something else like /usr/local/bin or /opt/bin depending
on the value of the --prefix option provided when Octave is
configured.

jwe