[GRASS-dev] [GRASS GIS] #2437: order parameters in g.remove window

GRASS GIS trac at osgeo.org
Mon Oct 20 08:38:39 PDT 2014

#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 hcho):

 Replying to [comment:20 wenzeslaus]:
 > Replying to [comment:19 hcho]:
 > > Replying to [comment:18 glynn]:
 > > > Replying to [comment:17 annakrat]:
 > > >
 > > > > In the previous version of g.remove, full name was working. I like
 the previous behavior more but of course the mapset is not really needed.
 > > >
 > > > Even so, a fully-qualified name should be accepted provided that the
 mapset is the current mapset. Code which executes GRASS modules should be
 able to use fully-qualified names throughout.
 > >
 > > This behavior is now fixed in r62303.
 > About "use fully-qualified names throughout" I though that it does not
 apply to the output (see also [http://lists.osgeo.org/pipermail/grass-
 dev/2014-September/070839.html mailing list], [http://osgeo-
 td5162363.html nabble link]). When removing a map, it is of course
 questionable if we are executing our write access (as in case of output)
 or if we are using existing map (which we can specify with mapset).

 I would say in this case, we're dealing with "input" or "existing" maps
 and g.remove should allow @MAPSET. IMO, names without @MAPSET only apply
 to "new" maps.

Ticket URL: <http://trac.osgeo.org/grass/ticket/2437#comment:22>
GRASS GIS <http://grass.osgeo.org>

More information about the grass-dev mailing list