[GRASS-dev] Re: [GRASS GIS] #178: g.copy/g.rename help message

GRASS GIS trac at osgeo.org
Mon Aug 22 04:16:17 EDT 2011


#178: g.copy/g.rename help message
-------------------------------------+--------------------------------------
 Reporter:  hcho                     |       Owner:  grass-dev@…              
     Type:  enhancement              |      Status:  new                      
 Priority:  minor                    |   Milestone:  7.0.0                    
Component:  Default                  |     Version:  svn-trunk                
 Keywords:  copy, rename, overwrite  |    Platform:  All                      
      Cpu:  Unspecified              |  
-------------------------------------+--------------------------------------
Changes (by lucadelu):

  * keywords:  => copy, rename, overwrite
  * platform:  => All
  * version:  unspecified => svn-trunk
  * cpu:  => Unspecified
  * milestone:  6.4.0 => 7.0.0


Comment:

 Replying to [comment:1 glynn]:
 > Replying to [ticket:178 hcho]:
 >
 > AFAICT, this is a limitation of the parser. The syntax of the various
 options is <old>,<new> but the parser doesn't allow multiple ->gisprompt
 settings.
 >
 > BTW, neither the terminal interactive mode nor the GUI understand the
 significance of the key_desc option.
 >
 > I doubt that this can be changed given the current parser interface and
 the way that g.copy/g.rename use it. Essentially, trying to use a single
 option for multiple purposes (e.g. both input and output) tends to fail
 for alternate modes (--help, --ui, etc).
 >
 > The only way to make this work with the current parser interface would
 be to have separate source and destination options for each type, with the
 source labelled "old" and the destination labelled "new".
 >
 > It would be nice to maintain a global list of cases which the parser
 doesn't handle well (or at all), for reference when we get around to
 designing a new type system for the parser.

 Is it possible to fix it for the GRASS 7 version?

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



More information about the grass-dev mailing list