Re: Octave.app for MacOSX released

[Norm Hecht]

No luck... I got the ASCII plot again.  Without the GNUTERM
environment variable, drawnow.m selects the dumb terminal
instead of trying gnuplot and its defaults.  It won't set
the dumb terminal option if getenv("DISPLAY") isn't empty,
but again, it's set when I check in the shell, but not
in Octave itself.

So tried eliminating putenv("GNUPLOT") from my octaverc
profile, and adding putenv(":0.0") instead, which worked.
BTW, I got the ":0.0" from a previous octave/gnuplot
setup--is that still a good choice?

I changed my .gnuplot file to this:

set terminal aqua 0 fname "Verdana"

so I could chanage the font.  Changing the command to
'set terminal aqua fname "Verdana"' causes an error
message about unknown variable fname.  The help in
gnuplot makes it look like the 0 is optional, though.

Hope this helps,

Norm


On Jul 6, 2007, at 9:50 AM, Thomas Treichl wrote:

> Norm Hecht schrieb:
> > Thomas,
> > I applied the patch (by hand, I couldn't get the patch command to
> > do it), and tried plotting.  I got the ASCII plot again, typed
> > getenv("GNUTERM") and found out it was blank, even though the
> > shell thought it was set.
>
> Ok, what about setting 'set terminal aqua' in the startup- 
> file .gnuplot in your HOME directory and *not* doing 'putenv 
> ("GNUTERM", "aqua")'. Does this work? Cf. http://www.gnuplot.info/ 
> docs/gnuplot.pdf pp. 34
>
> > I put the putenv() command in my octaverc so it's automatically
> > applied now.  Any ideas on how to get rid of the first-plot error?
>
> Not at the moment, it sound's like a platform independent problem  
> for me but 'am not sure. If it is then I think it has already been  
> reported on the list and is fixed with the current CVS. I can have  
> a look for it on the weekend...
>
>   Thomas