[GRASS5] [bug #3710] (grass) store GUI commands in Grass history - same as CLI
Maciek Sieczka via RT
grass-bugs at intevation.de
Mon Oct 10 09:51:22 EDT 2005
First of all - I'm changing the subject so it reflects what I mean better.
Sorry for missunderstanding. Please read below.
Michael Barton wrote:
> Although the d.m layers don't write to the command history upon display,they
> CAN be saved as a "group".
I don't mean to store the d.m layer-command into history, only the command
invoked from GUI.
I mean this, eg.: I call v.out.ogr&, GUI pops up, I select options, execute
and the full command syntax is stored in the Grass history - like if I called
the command from CLI.
Glynn, does this change anything? Do the limitations for d.m layer commands
you described apply to Grass commands invoked from their GUIs too? Or could
they be stored in Grass history easier than d.m commands?
> To get the commands to save to the command history, you'd need to write a
> shell script with the same commands. This is pretty easy because, when you
> push the display button, all the commands get written to the terminal.
When talking of this - it is an annoying feature actually IMO. d.m should not
mess with main Grass terminal. Grass terminal should be left for CLI only if
-------------------------------------------- Managed by Request Tracker
More information about the grass-dev