[GRASS-dev] Re: diff to start wingrass with GUI + com.exe terminal [was: Re: [winGRASS] (no subject)]

Moritz Lennert mlennert at club.worldonline.be
Mon May 21 08:13:14 EDT 2007

On 21/05/07 13:55, Hamish wrote:
> Paul Kelly wrote:

>> I was going by the thinking that it was a historical accident that GUI
>> and command-line were available at the same time with Init.sh, and
>> with improvements to the GUI it would eventually incorporate a sort
>> of command-line interface (like an improved gronsole.tcl) and a
>> separate command-line Window wouldn't be necessary, but if we feel
>> that it's good  to have it there to emphasis the power of GRASS then
>> we can definitely put it into init.bat too.
> As you hint to, support is already (sort of) there in a non-obvious way
> from gronsole.tcl, just type any shell command in the bottom part of the
> "Output - GIS.m" window and click [Run]. Maybe it just needs some
> tidying and a GRASS> prompt or something? Or is that always going to
> suck badly versus a true <xterm|cmd.exe> window?

As long as it lacks any programming elements, such as loops and if/then 
I would say, yes.
Just the possibility of typing a GRASS command does not replace all the 
wealth of a shell.

> Does this start to violate concurrent mapset use?

How ?


More information about the grass-dev mailing list