#2437: order parameters in g.remove window
--------------------------------------------------+-------------------------
Reporter: pvanbosgeo | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.1.0
Component: Default | Version: unspecified
Keywords: g.list, g.remove, g.mlist, g.mremove | Platform: All
Cpu: Unspecified |
--------------------------------------------------+-------------------------
Comment(by glynn):
Replying to [comment:20 wenzeslaus]:
> About "use fully-qualified names throughout" I though that it does not
apply to the output
No.
You're only supposed to be able to create, remove, replace or modify maps
in the current mapset. But that doesn't mean that you can't use a fully-
qualified name, only that the @mapset part has to be the current mapset.
Requiring the use of unqualified names in such cases imposes a burden on
scripts, as they need to know that a map name refers to an output. When
map names are obtained from the output of other modules, they may be
provided as fully-qualified names, requiring the script to strip the
mapset.
Also, an unqualified name doesn't necessarily refer to a map in the
current mapset. It refers to the first such map found in the mapset search
path. At present, the current mapset is forcibly added to the head of the
search path. This is a workaround for bugs in numerous modules and scripts
which assume that this will always be the case, but it shouldn't be relied
upon.
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/2437#comment:23>
GRASS GIS <http://grass.osgeo.org>
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
