I’ve noticed this before but hesitated to mention it. But still it’s kind of weird.
If you run g.mlist (at least run through the GUI) you get messages like this sent to the terminal
GRASS_INFO_WARNING(14538,1): Illegal filename <a_>. Character <> not allowed.
But of course the whole idea of g.mlist is to let you use characters like “*”
g.mlist works fine. It just generates these bogus warnings.
Michael
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University
On Mon, Feb 4, 2013 at 7:38 AM, Michael Barton <Michael.Barton@asu.edu> wrote:
I've noticed this before but hesitated to mention it. But still it's kind of
weird.
If you run g.mlist (at least run through the GUI) you get messages like this
sent to the terminal
GRASS_INFO_WARNING(14538,1): Illegal filename <a_*>. Character <*> not
allowed.
But of course the whole idea of g.mlist is to let you use characters like
"*"
g.mlist works fine. It just generates these bogus warnings.
These bogus warnings don't come from the module, they come from the
wxGUI. Similar for multiple inputs, there the GUI complains about ","
being an illegal character. I am not sure if the GUI should do option
checking itself, the parser is doing that anyway.
2013/2/4 Markus Metz <markus.metz.giswork@gmail.com>:
On Mon, Feb 4, 2013 at 7:38 AM, Michael Barton <Michael.Barton@asu.edu> wrote:
I've noticed this before but hesitated to mention it. But still it's kind of
weird.
If you run g.mlist (at least run through the GUI) you get messages like this
sent to the terminal
GRASS_INFO_WARNING(14538,1): Illegal filename <a_*>. Character <*> not
allowed.
But of course the whole idea of g.mlist is to let you use characters like
"*"
g.mlist works fine. It just generates these bogus warnings.
These bogus warnings don't come from the module, they come from the
wxGUI. Similar for multiple inputs, there the GUI complains about ","
being an illegal character. I am not sure if the GUI should do option
checking itself, the parser is doing that anyway.