|
From: Petr M. <mi...@ph...> - 2005-10-03 13:30:52
|
>> 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
>> terminals.
>>
>
> 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.
In summary, there are cases where modifiable options are preferred, and
other where sticky options would be preferred.
Possible solutions:
- "set term{options} {no}stickyoptions"
- set term {xxx} default or reset term or unset termoptions
This would require an update to terminals. IMHO, it would be quite easy.
I propose this:
change
TERM_PUBLIC void XXX_options __PROTO((void));
to
TERM_PUBLIC void XXX_options __PROTO((int flag));
and if (flag==0) execute the current code, and if (flag==1) then reset all
options to default values.
It needs to a small update to all terminals, but is easy to do.
> 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...
Options are particular for a given terminal, not for different terminals. So
the above case won't happen.
---
PM
|