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

Hamish hamish_nospam at yahoo.com
Mon May 21 07:55:13 EDT 2007

Paul Kelly wrote:
> But, I suppose maybe it would be a gentle introduction to command-line
> GRASS for Windows users if the other Window was open in the background
> and they were able to use it. It would complicate things though, as
> they would have to type exit in the command-line Window to exit it
> *after* shutting down gis.m; I worry that it would make GRASS look
> cumbersome and awkward.

I agree, either launch the GUI or text mode, not both. But allow
starting the GUI from text mode if the user wants that, or vice versa.

> Was thinking perhaps an option button in gis_set.tcl (the first Tcl/Tk
> window that allows you to select the location) to open either GUI or
> Command-line Windows or both might be a nice idea?

How about a menu item to open a terminal in the main File-> or Config->
menus? Or a button on the GIS Manager toolbar? (of course "-text" on
startup would get you there without the GUI as well)

> 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?
Does this start to violate concurrent mapset use?


More information about the grass-dev mailing list