[GRASS5] [bug #3177] (grass) g.gisenv

Markus Neteler neteler at itc.it
Wed Apr 27 11:29:07 EDT 2005

On Sat, Apr 23, 2005 at 12:21:13AM +0200, Request Tracker wrote:
> this bug's URL: http://intevation.de/rt/webrt?serial_num=3177
> -------------------------------------------------------------------------
>   $ g.gisenv help
>   Description:
>    Outputs the user's current GRASS variable settings.
> Sets them also too, no?

Fixed in both 6.1-CVS and 6.0.1-CVS/release branch.
>   Usage:
>    g.gisenv [get=VARIABLE] [set="VARIABLE=value"] [store=name]
>   Parameters:
>       get   GRASS variable to get
>       set   GRASS variable to set
> Why do you say "set" twice?

why not?

>     store   Where GRASS variable is stored
>             options: gisrc,mapset
>             default: gisrc
> Also man g.gisenv doesn't mention GRASS_GUI. One wants to know all the
> possible choices.  Also mention GRASS_DB_ENCODING, etc.

 "Possible variable names depend on the user's system, see variables list for details."
 -> http://grass.itc.it/grass60/manuals/html60_user/variables.html

> The man page says
>        To disable debugging messages, DEBUG must be set back to 0:
>        g.gisenv set="DEBUG=0"
> Well for me, I got lots of
>   D5/15: Get_location_with_pointer2(): cmd = 2
> on the screen still, g.gisenv will not fix things until the user
> restarts grass.  So say so.

You are using an outdated version of GRASS.
> Maybe if the poor choice to race the CPU at 100% when waiting for
> mouse input for all grass programs had not been made, the D5/15
> message flood wouldn't be so devastating.

The CPU/d.* issue was already discussed a couple of times.


More information about the grass-dev mailing list