[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 17:34:31 EDT 2007


On Mon, May 21, 2007 23:03, Michael Barton wrote:
>
>
> On 5/21/07 12:52 PM, "Moritz Lennert" <mlennert at club.worldonline.be>
> wrote:
>
>> On Mon, May 21, 2007 17:23, Michael Barton wrote:

>>> Beyond an interactive terminal, what would a 'serious integrated CLI'
>>> entail?
>>>
>>
>> Scripting, i.e. a certain level of programming instructions which allow
>> you to combine different grass commands with other shell commands.
>> Something which when it becomes really ripe and useful can become a
>> grass
>> script à la d.vect.thematic, but which many people just homecook to use
>> for their own convenience.
>
> Currently from the CLI in gronsole you can run any script in CLI mode
> (i.e.,
> typing all arguments from the CLI). In the wxgrass command line you can do
> this and  you can also just type the name of the GRASS script/command and
> get the autogenerated dialog launched, just like you would from the
> terminal.
>
> AFAICT, you can do this for any bash or python script (or whatever the
> shell
> can do something with).
>

Yes, if you have a preexisting script. But you cannot type and run
something like (nonesense script for demonstration):

for val, col in $valnames
do
  d.vect map=X fcolor=$col cat=$val
done

You would have to save it as a script in your PATH and then launch it as
such.

Moritz




More information about the grass-dev mailing list