|
From: Ethan A M. <merritt@u.washington.edu> - 2006-04-16 20:43:18
|
On Sunday 16 April 2006 12:21 pm, Petr Mikulik wrote: > BTW, "set term pop" for those things will fail if your "set term push"ed > terminal is postscript, for example. I was under the impression that 'set term push/pop' was a stack, but I see that I was wrong. The truth is that I have never used this mechanism. > > 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. OK. But then the name "GNUTERM" is slightly misleading. Should it rather be "DEFAULT_TERMINAL" or something like that? By the way, saving the value of GNUTERM internally allows this rather neat trick, where the terminal options are kept also: [1] setenv GNUTERM "post eps solid color lw 2" [2] gnuplot ... gnuplot> set term <something_else> gnuplot> [... do a bunch of stuff ...] gnuplot> set macros gnuplot> set term @GNUTERM gnuplot> show term Terminal type set to 'postscript' Options are 'eps noenhanced defaultplex \ leveldefault color colortext \ solid dashlength 1.0 linewidth 2.0 butt \ palfuncparam 2000,0.003 \ "Helvetica" 14 ' -- Ethan A Merritt Biomolecular Structure Center University of Washington, Seattle 98195-7742 |