So far, I've only seen this in Vista and am wondering if anyone else has seen it. Using the nightly build from 2 February.
From the command line, type the name of a script, like r.blend, without arguments
Instead of the GUI popping up, there is an error complaining about the lack of arguments.
It's like g.parser is not being invoked.
i can confirm this changed behaviour, typing a command without arguments and no GUI popping up.
tested on WinVista32 with self compiled Grass64 and Grass65
Helmut
______________________________________________________
GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://movieflat.web.de
> From the command line, type the name of a script, like
> r.blend, without arguments
> Instead of the GUI popping up, there is an error
> complaining about the lack of arguments.
>
> It's like g.parser is not being invoked.
Helmut wrote:
i can confirm this changed behaviour, typing a command
without arguments and no GUI popping up.
tested on WinVista32 with self compiled Grass64 and
Grass65
>So far, I've only seen this in Vista and am wondering if anyone else has seen it. Using the nightly build from 2 February.
>
>From the command line, type the name of a script, like r.blend, without arguments
>Instead of the GUI popping up, there is an error complaining about the lack of arguments.
>
>It's like g.parser is not being invoked.
i can confirm this changed behaviour, typing a command without arguments and no GUI popping up.
tested on WinVista32 with self compiled Grass64 and Grass65
Note that if GRASS_GUI is tcltk, it won't work, due to G_popen() not
working at all on Windows (execl() works like on Unix, i.e. it doesn't
return if it succeeds; but unlike Unix, Windows doesn't have fork()).
On Thu, Feb 4, 2010 at 9:16 PM, Glynn Clements <glynn@gclements.plus.com> wrote:
Helmut Kudrnovsky wrote:
>So far, I've only seen this in Vista and am wondering if anyone else has seen it. Using the nightly build from 2 February.
>
>From the command line, type the name of a script, like r.blend, without arguments
>Instead of the GUI popping up, there is an error complaining about the lack of arguments.
>
>It's like g.parser is not being invoked.
i can confirm this changed behaviour, typing a command without arguments and no GUI popping up.
tested on WinVista32 with self compiled Grass64 and Grass65
Note that if GRASS_GUI is tcltk, it won't work, due to G_popen() not
working at all on Windows (execl() works like on Unix, i.e. it doesn't
return if it succeeds; but unlike Unix, Windows doesn't have fork()).
> Note that if GRASS_GUI is tcltk, it won't work, due to G_popen() not
> working at all on Windows (execl() works like on Unix, i.e. it doesn't
> return if it succeeds; but unlike Unix, Windows doesn't have fork()).
>
> Using the new G_popen() from 7.0 is one option.
... another backport project?
Resolved in r40834 (6.5) by replacing all uses of G_popen() (there are
only three, all in lib/gis) with popen().
On Sat, Feb 6, 2010 at 1:04 AM, Glynn Clements <glynn@gclements.plus.com> wrote:
Markus Neteler wrote:
> Note that if GRASS_GUI is tcltk, it won't work, due to G_popen() not
> working at all on Windows (execl() works like on Unix, i.e. it doesn't
> return if it succeeds; but unlike Unix, Windows doesn't have fork()).
>
> Using the new G_popen() from 7.0 is one option.
... another backport project?
Resolved in r40834 (6.5) by replacing all uses of G_popen() (there are
only three, all in lib/gis) with popen().