[GRASSLIST:8551] Re: d.m - commands output pollute the Grass
terminal
Michael Barton
michael.barton at asu.edu
Sat Oct 8 12:35:18 EDT 2005
Thanks. I'll try this in my next updates.
Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
Arizona State University
Tempe, AZ 85287-2402
phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton
> From: Glynn Clements <glynn at gclements.plus.com>
> Date: Sat, 08 Oct 2005 10:29:22 +0100
> To: Michael Barton <michael.barton at asu.edu>
> Cc: Maciek Sieczka <werchowyna at epf.pl>, <grasslist at baylor.edu>
> Subject: Re: [GRASSLIST:8545] Re: d.m - commands output pollute the Grass
> terminal
>
>
> Michael Barton wrote:
>
>>> I understand, that's good. But could there be a permanent, *separate*
>>> terminal for output from d.m commands? It could be the small, neat one - the
>>> same which pops up when we query raster layers from d.m.
>>>
>>> Currently my Grass terminal looks like a Matrix screesaver when I redraw 20
>>> layers in d.m. Main terminal should be for CLI, GUI should have a separate
>>> text output, I guess.
>>
>> This is a good idea but I don't know how to redirect this output to a
>> separate terminal. Anyone have a suggestion?
>
> xterm -e d.m &
>
> or, if xterm is setuid:
>
> xterm -e $GISBASE/etc/grass-run.sh d.m &
>
> --
> Glynn Clements <glynn at gclements.plus.com>
More information about the grass-user
mailing list