[Top][All Lists]

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

Re: pslatex terminal output--Problem identified.

From: Dmitri A. Sergatskov
Subject: Re: pslatex terminal output--Problem identified.
Date: Sun, 02 Oct 2005 13:02:44 -0600
User-agent: Mozilla Thunderbird 1.0.6-1.4.1 (X11/20050721)

Ethan A Merritt wrote:
On Sunday 02 October 2005 09:54 am, Dmitri A. Sergatskov wrote:

Petr Mikulik wrote:

IMHO, these permanent options are a good idea even for interactive
driving: for example, you can set terminals to "enhanced" mode in your
.gnuplot file and don't need to do this in the driving program.

I would need to do it
if somewhere in the middle of the session the mode has changed
to "noenhanced" for whatever reason...

This is already supported in 4.1 via the "set termoption" command.
"set termoption enhanced" will flip the current terminal into
enhanced mode without changing anything else.

As of now only a limited subset of the possible terminal options
can be changed mid-flight in this way: {no}enhanced and the
default font.  Other options may be added, subject to the
concern that the option must have the same meaning for multiple

I guess I am not being clear. As I said, the problem with sticky options
is that it is impossible to predict what setting one going to get when
issued a command "set term post color". Let's say I am using a gnuplot
as a graphical backend to some program and I want to have a command "print" that does "set term post color; set output 'file.out'; replot". The only way I can get a consistent format of the output graph if I specify explicitly _all_ the options to the "set term postscript" thing.
One example is when one does "set term post eps" and later
"set term pslatex". Since the "eps" option is sticky it messes up the
pslatex terminal...



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

Octave's home on the web:
How to fund new projects:
Subscription information:

reply via email to

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