[GRASS-dev] Shell scripts

Markus Neteler neteler at osgeo.org
Fri Nov 27 02:33:38 EST 2009

On Fri, Nov 27, 2009 at 2:56 AM, Glynn Clements
<glynn at gclements.plus.com> wrote:
> Michael Barton wrote:
>> > If you want to be able to control the GUI from the command line, that
>> > should be dealt with as an infrastructure issue, not by creating
>> > wrappers around individual commands.
>> >
>> > I can deal with the display/driver libraries, and with generic Python
>> > IPC, but some of it will need the involvement of someone who
>> > understands the GUI.
>> Winter break is near and I'll be laid up for a week. So I might be
>> able to help.
>> Controlling the GUI from the command line is a contradiction in
>> interface terms. Perhaps you really mean displaying a map from the
>> command line?
> I mean controlling the GUI, i.e. being able to modify the list of
> displayed maps. That's what the p.* scripts appear to be doing.

Yes, like what the d.* commands did with x0 etc.
I regularly enjoy the beauty of shell history which I would
not have using the (pure) GUI since clicks aren't registered.


More information about the grass-dev mailing list