Details Ticket 3177


Comment | Reply | Take | Open


Serial Number 3177
Subject g.gisenv
Area none
Queue grass
Requestors jidanni@jidanni.org
Owner none
Status resolved
Last User Contact Wed Apr 27 17:29:11 2005 (3 yr ago)
Current Priority 30
Final Priority 70
Due No date assigned
Last Action Wed Apr 27 17:29:20 2005 (3 yr ago)
Created Sat Apr 23 00:21:13 2005 (3 yr ago)

Transaction History Ticket 3177


Sat, Apr 23 2005 00:21:13    Request created by jidanni@jidanni.org  
Return-Path <jidanni@jidanni.org>
Delivered-To grass-bugs@lists.intevation.de
To grass-bugs@intevation.de
Subject g.gisenv
From Dan Jacobson <jidanni@jidanni.org>
Date Sat, 23 Apr 2005 04:54:22 +0800
Message-ID <87ekd2h6rl.fsf@jidanni.org>
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
X-Spam-Status No, hits=-4.9 tagged_above=-999.0 required=3.0 tests=BAYES_00
X-Spam-Level
  $ g.gisenv help

  Description:
   Outputs the user's current GRASS variable settings.
Sets them also too, no?

  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?
    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.

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.

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.


Wed, Apr 27 2005 17:29:11    Mail sent by neteler@itc.it  
Return-Path <neteler@itc.it>
Delivered-To grass-bugs@lists.intevation.de
Date Wed, 27 Apr 2005 17:29:07 +0200
From Markus Neteler <neteler@itc.it>
To Request Tracker <grass-bugs@intevation.de>
Cc grass5@grass.itc.it
Subject Re: [GRASS5] [bug #3177] (grass) g.gisenv
Message-ID <20050427152907.GY19598@thuille.itc.it>
Mail-Followup-To Request Tracker <grass-bugs@intevation.de>, grass5@grass.itc.it
References <20050422222113.88B991005DB@lists.intevation.de>
Mime-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Disposition inline
In-Reply-To <20050422222113.88B991005DB@lists.intevation.de>
User-Agent Mutt/1.4.1i
X-Spam-Status No, hits=-4.9 tagged_above=-999.0 required=3.0 tests=BAYES_00
X-Spam-Level
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.

RTFM:
 http://grass.itc.it/grass60/manuals/html60_user/g.gisenv.html
 "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.

Markus


Wed, Apr 27 2005 17:29:20    Status changed to resolved by mneteler  
Comment | Reply | Take | Open

You are currently authenticated as guest.
[Show Configuration] [Login as another user]

Users Guide - Mail Commands - Homepage of RequestTracker 1.0.7 - list any request