Thanks. Your suggestion does indeed stop the plot from appearing on the screen -- but when run in the background, the process still stops.
BTW, I shouldn't have said it hangs if run in the background -- it goes into the "stopped" state. And further experiments have revealed that a script that does plotting, but does not do "print", does not go into "stopped". Even if I omit the part that sets visible off. It only stops if I include a "print."
Maybe I should write a bug report -- I can't think of any good reason why "print" should have to run in the foreground.
- Dave Cottingham
----- Original Message -----
From: "Ben Abbott" <address@hidden>
To: address@hidden
Cc: address@hidden
Sent: Tuesday, September 29, 2009 3:58:52 PM GMT -05:00 US/Canada Eastern
Subject: Re: another "gset term" replacement question
> On Tuesday, September 29, 2009, at 01:28PM, <address@hidden
> > wrote:
>
> I often have a need to run octave scripts in the background,
> sometimes scripts that make plots. With octave 2.x, I would preceed
> any such plotting with "gset term postscript".
>
> Now that gset is gone, I do the plotting and the use "print -dpsc"
> to put it into a postscript file. But if I try to run such a script
> in background, it hangs when it gets to the plotting.
>
> How can I direct the script to make the plot postscript in the first
> place? Or is there any other way to stop it from hanging? Is there
> any way to control where octave's invocation of gnuplot tries to put
> the plot?
>
> Thanks,
> Dave Cottingham
To produce a postscript output ...
print -dpsc file.ps
To suspend generation of figures on screen, you can try ...
close all
set (0, "defaultfigurevisible", "off")
To continue with plots to the screen ...
close all
set (0, "defaultfigurevisible", "on")
Ben