help-octave
[Top][All Lists]
Advanced

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

Re: Revealing gnuplot input?


From: Paul Kienzle
Subject: Re: Revealing gnuplot input?
Date: Mon, 20 May 2002 17:32:24 -0400

On Mon, May 20, 2002 at 04:12:55PM -0500, John W. Eaton wrote:
> On 20-May-2002, Tom Kornack <address@hidden> wrote:
> 
> | Thanks very much to the developers for maintaining such beautiful 
> | software. I use it daily.
> | 
> | I'm a relatively inexperienced octave user running on Mac OS X with 
> | Aquaterm. It's a spectacular combination for this platform. My code 
> | works just fine when I set my terminal to x11. However, I would like to 
> | use the multiplot commands with Aquaterm, and I'm running afoul of the 
> | Aquaterm adapter. How can I see the gnuplot script that it's trying to 
> | run when I invoke the octave wrappers? I'd like to bring the issue to 
> | the Aquaterm developers. Has anyone run into a similar problem?
> 
> If you want to see what commands Octave is sending to gnuplot try
> 
>   gnuplot_binary = "tee /tmp/some-file | gnuplot"
> 
> before any plot commands, then Octave will send the plot commands to
> /tmp/some-file and gnuplot.  When you are done with your plotting
> commands, you can look at /tmp/some-file and see what commands were
> sent to gnuplot.

I don't know if this will work for you, but I can start a new terminal window,
and type 'tty' to get the name of the device, then use this device as the
/tmp/some-file in the previous command.  Then the commands are displayed
immediately.  Alternatively, you could try 'tail -f /tmp/some-file', which
has the same effect, but requires a temporary file.


Paul Kienzle
address@hidden



-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:  http://www.octave.org
How to fund new projects:  http://www.octave.org/funding.html
Subscription information:  http://www.octave.org/archive.html
-------------------------------------------------------------



reply via email to

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