[GRASS-dev] Shell scripts

[Michael Barton]

Right you are. I hadn't mentioned this because I thought it wasn't  
working and didn't have time to look into it. But I only had the wrong  
syntax.

The d.* commands don't produce a history in the output console, but  
that is easily changed.

A couple of additional modifications would give this more the feel of  
the system console.

1) Have the typed input go into the styled text window (output  
console) instead of a separate command entry box
2) Have the styled text window bind carriage returns so that it will  
treat any line under the cursor as a "command" to parse when return is  
pressed.

As Glynn says, this is not exactly the same as a system terminal, but  
it comes pretty close in functionality.

Michael

On Dec 1, 2009, at 5:54 AM, Martin Landa wrote:

> Hi,
>
> 2009/12/1 Michael Barton <Michael.Barton at asu.edu>:
>
> [...]
>
>> On the other hand, if these folks DO want to use the wxPython GUI  
>> (and all
>> the interactive tools on the canvas) but simply want to be able to  
>> get maps
>> displayed in the canvas by typing commands instead of adding them  
>> to the
>> layer manager, then I think the better way to go is to enhance the  
>> wxPython
>> console. This solution could be of interest to power users on all  
>> platforms.
>
> It already works, try to type in wxGUI prompt, e.g. `d.rast
> map=elevation.dem`. Anyway I think that something like `d.mon wx0`
> would be usable.
>
> Martin
>
> -- 
> Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa