this bug's URL: http://intevation.de/rt/webrt?serial_num=4186
-------------------------------------------------------------------------
Subject: grass61 command: all parameters specified or none of them
Platform: GNU/Linux/x86
grass obtained from: CVS
grass binary for platform: Compiled from Sources
GRASS Version: 20060316
Documentation and help for the command grass61 specifies that:
You must specify one of the following
MAPSET
LOCATION_NAME/MAPSET
GISDBASE/LOCATION_NAME/MAPSET
In fact, at the commandline, only the last option works:
GISDBASE/LOCATION_NAME/MAPSET
the other options are ambiguous and result in a "Not a valid Location" error.
-------------------------------------------- Managed by Request Tracker
H_B
2
this bug's URL: http://intevation.de/rt/webrt?serial_num=4186
---------------------------------------------------------------------
Subject: grass61 command: all parameters specified or none of them
Platform: GNU/Linux/x86
grass obtained from: CVS
grass binary for platform: Compiled from Sources
GRASS Version: 20060316
Documentation and help for the command grass61 specifies that:
You must specify one of the following
MAPSET
LOCATION_NAME/MAPSET
GISDBASE/LOCATION_NAME/MAPSET
In fact, at the commandline, only the last option works:
GISDBASE/LOCATION_NAME/MAPSET
the other options are ambiguous and result in a "Not a valid Location"
error.
This is uncorrect. It works fine but you have to be in the correct
directory.
e.g. these all work:
cd $MAPSET
grass61 `pwd`
# this works but mapset name in g.gisenv is ".", which is bad
cd $MAPSET
grass61 .
cd $LOCATION
grass61 $MAPSET
cd $GISDBASE
grass61 $LOCATION/$MAPSET
and finally
grass61 $GISDBASE/$LOCATION/$MAPSET
the trick is you have to be in the correct part of the file system.
e.g. if $MAPSET = $USER, grass61 $USER from /home could very well be
ambiguous.
This seems like a good time to again call for an enhancement to the
TclTk startup screen: double clicking on a mapset name should imply
"continue".
Hamish