|
From: Petr M. <mi...@ph...> - 2006-04-16 19:22:03
|
>>> perhaps "set term screen <num>", where "screen" is taken from
>>> GNUTERM, and <num> is ignored for terminals that don't support multiple windows.
>
> exactly
>
>> Screen terminals should be unified so that they are capable of
>> set terminal screen {<n>}
>> {title "<string>"}
>> {{no}enhanced}
>> {font <fontspec>}
>> {{no}persist}
>> {{no}raise}
>> {close}
>
> I agree with this, but the mechanism is already in place:
> set term pop
> set termoption enhance font "Times,11" ...
I think it is much more logical to write
set term screen title "hello"
then doing those setting as
set term pop; set termoptions ...
BTW, "set term pop" for those things will fail if your "set term push"ed
terminal is postscript, for example. These commands are intended for saving
the *current* terminal e.g. before printing, not for restoring the default
screen terminal (yes it is available as "set term pop" would be undefined
otherwise).
Thus I propose, at the startup point of gnuplot, where the initial "set term
pop/push" is pushed, to "link" the "screen" terminal. Would a simple strcpy
suffice or how to associate them?
>> supports new string function getenv('GNUTERM')?
> What do you mean "available"?
> The value of GNUTERM is stored as the terminal name on entry.
> So if you immediately do a "set term push", then you have
> saved whatever the GNUTERM default was and can recover it
> later with "set term pop".
> But yes, we could also copy it into a udv called GNUTERM.
> That is so easy that I might as well just go ahead and add it :-)
I see you've added it ... I tried it ... However, this variable is undef if
user doesn't use GNUTERM env. variable. I think gnuplot's GNUTERM should
contain the name of the startup terminal then -- otherwise this variable
does not make any sense.
---
PM
|