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

GRASS GIS trac at osgeo.org
Tue Oct 28 20:49:06 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 annakrat):

 Replying to [comment:25 hcho]:
 > > Another suggestion is to use -f only for pattern option. When using
 names, it wouldn't require force flag for the actual removing of the maps.
 Any opinion on that?
 > IMO, that's not a good idea because of inconsistent behaviors. If we
 want any confirmation when using patterns, the force flag should be used
 if "any" of {{{pattern=}}} or {{{exclude=}}} is used.
 > {{{
 > # Patterns used => use -f flag
 > g.remove -f rast pattern=... exclude=...
 > g.remove -f rast pattern=... ignore=...
 > g.remove -f rast names=... exclude=...
 > # No patterns used => no -f flag; this is inconsistent and can be
 confusing when using patterns.
 > g.remove rast names=... ignore=...
 > }}}

 I mostly agree, although inconsistent doesn't necessarily mean not

 > If it's annoying to run g.remove GUI twice, what about this? In a single
 GUI run, show output and ask the user if they want to delete them.

 I am generally against implementing any special things for one module
 (which has autogenerated dialog).

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

More information about the grass-dev mailing list