Hamish wrote:
> > > The opt->options part of the parser only allows
> > through full names.
>
> Moritz Lennert wrote:
> > But it should be possible to parse the answer taking into account
> > shorter versions. See, for example, how type_opt is parsed on lines
> > 478ff in display/d.vect/main.c
d.vect is not a good example, as it should be using
Vect_option_to_types(). No wonder that GRASS has so many LOC - lots of
duplication ;)
Maris.
2008/10/1, Moritz Lennert <[EMAIL PROTECTED]>:
> On 01/10/08 02:55, Hamish wrote:
>> Markus:
>>> (Un)related: could be have
>>> g.gui wx
>>> as a shortc
> > The opt->options part of the parser only allows
> through full names.
Moritz Lennert wrote:
> But it should be possible to parse the answer taking into account
> shorter versions. See, for example, how type_opt is parsed on lines
> 478ff in display/d.vect/main.c.
sure there's code in d.vec
On 01/10/08 02:55, Hamish wrote:
Markus:
(Un)related: could be have
g.gui wx
as a shortcut? "wxpython" is really hard to type...
The opt->options part of the parser only allows through full names.
But it should be possible to parse the answer taking into account
shorter versions. See, for e
Markus:
> (Un)related: could be have
> g.gui wx
> as a shortcut? "wxpython" is really hard to type...
The opt->options part of the parser only allows through full names.
My feeling is that adding shortcuts like that to the option list are
a really ugly solution, e.g. units="mi","miles","m","meter
On Tue, Sep 30, 2008 at 10:07 AM, Moritz Lennert
<[EMAIL PROTECTED]> wrote:
> On 30/09/08 00:33, Richard Chirgwin wrote:
>>
>> All,
>>
>> I'm taking a look at the Python GUI, and wanted to make this comment.
>>
>> Unlike the tcltk GUI, which leaves an open command line after it starts,
>> the Pytho
On 30/09/08 00:33, Richard Chirgwin wrote:
All,
I'm taking a look at the Python GUI, and wanted to make this comment.
Unlike the tcltk GUI, which leaves an open command line after it starts,
the Python GUI does not. This is an issue if you want to run a module
that the GUI hasn't noticed (in my
All,
I'm taking a look at the Python GUI, and wanted to make this comment.
Unlike the tcltk GUI, which leaves an open command line after it starts,
the Python GUI does not. This is an issue if you want to run a module
that the GUI hasn't noticed (in my case, r.in.onearth) - because you
can't bypa
