Re: GPGET('terminal')

[Petr M. <mi...@ph...>]

>> a = GPGET("terminal")   =>  return "x11"
>> a = GPGET("termoptions")   =>  return "enhanced noraise"
>> xmin = GPGET("xmin")    =>  return min of xrange of the last plot
>> ... GPGET("xmax"), "y2min", "cbmin", etc.
>
>> Only few variables, the most important, should be availabe now -- others
>> could be added on user's request any later, without poluting the user
>> space with new var/funcs.
>
> I'm not convinced that polluting the name space is a problem.
> We could simply agree to use only variables beginning with
> MOUSE_ or GPVAL_ or FIT_ or whatever, and document that users should
> avoid creating private variables starting with these character strings.
>
> Exporting a new internal variable as a user-visible one requires only
> 3 lines of code. Parsing for your proposed GPGET option would be more
> cumbersome, I think, and would require making all exportable variables
> global.

I have implemented it as you've proposed, see SF patch
 	1488448  User-available GPVAL_ variables

This patch implements user-available GPVAL_ variables, like GPVAL_X_MIN, 
GPVAL_X_MAX, GPVAL_Y_MIN, ...

Type
     show var all
to display those variables related to the last plot.

---
PM