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

[GRASS GIS]

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

 Replying to [comment:29 annakrat]:
 > Replying to [comment:28 hcho]:
 > > Replying to [comment:27 mlennert]:
 > > > Replying to [comment:26 annakrat]:
 > > > > I am generally against implementing any special things for one
 module (which has autogenerated dialog).
 > > >
 > > > +1
 > > >
 > > > Moritz
 > >
 > > Yeah.. +1 too. What about just getting rid of that flag completely and
 using g.list instead? While updating python scripts, I found it's just too
 much typing to add flags="f" every time and it doesn't make much sense in
 scripting anyway. Since the API of g.remove is compatible with g.list API
 as far as search patterns are concerned, it's a matter of changing module
 names. Is it too dangerous?
 >
 > I am afraid it is. Especially when users are used to it from the
 previous interface. Using -f flag only when using pattern/exclude would
 make more sense if want to avoid using it every time, but I understand why
 you don't like it. Some more input from others would be appreciated...

 I don't mind having the -f flag as extra security, even though it does add
 typing an extra 3 characters to the former use of g.remove.

 +1 for keeping the -f for all types of map selection.


 Moritz

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