[GRASS-dev] [GRASS GIS] #2099: G_OPT_M_COLR not recognized in Python script

#2099: G_OPT_M_COLR not recognized in Python script
---------------------------------+------------------------------------------
Reporter: annakrat | Owner: grass-dev@…
     Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: LibGIS | Version: svn-trunk
Keywords: color table, parser | Platform: Linux
      Cpu: Unspecified |
---------------------------------+------------------------------------------
When I try to use standardized option G_OPT_M_COLR (color tables) in a
Python script, I get only:

{{{
myscript --help

Description:
...
Usage:
...
ERROR: Option key not defined
}}}

and

{{{
myscript --interface-description

...
<parameter name="(null)" type="string" required="no" multiple="no">
         </parameter>
...

}}}

This affects t.rast.colors. G_OPT_M_COLR is defined here:

[1]
http://trac.osgeo.org/grass/browser/grass/trunk/lib/gis/parser_standard_options.c#L619

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/2099&gt;
GRASS GIS <http://grass.osgeo.org>

#2099: G_OPT_M_COLR not recognized in Python script
---------------------------------+------------------------------------------
Reporter: annakrat | Owner: grass-dev@…
     Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: LibGIS | Version: svn-trunk
Keywords: color table, parser | Platform: Linux
      Cpu: Unspecified |
---------------------------------+------------------------------------------

Comment(by wenzeslaus):

`t.rast.colors --interface-description` seems to work. `... | grep null`
gives nothing. `t.rast.colors --help` gives full output and no error:
{{{
Description:
...
Keywords:
...
Usage:
  t.rast.colors [-rwlngae] input=name [color=string] [raster=name]
    [volume=name] [rules=name] [--help] [--verbose] [--quiet]

Flags:
...
Parameters:
...
}}}

Test script with `G_OPT_M_COLR` should be created.

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/2099#comment:1&gt;
GRASS GIS <http://grass.osgeo.org>