[GRASS-dev] running commands in background

[Michael Barton]

I agree. I can think of instances where it would be useful to disable
unnecessary output on a particular file but not want to turn it off for all
of them. But this would entail adding a strict quiet flag to all. Maybe a
lot of work.

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics and Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton


> From: Glynn Clements <glynn at gclements.plus.com>
> Date: Thu, 25 May 2006 21:46:55 +0100
> To: Michael Barton <michael.barton at asu.edu>
> Cc: <grass-dev at grass.itc.it>
> Subject: Re: [GRASS-dev] running commands in background
> 
> 
> Michael Barton wrote:
> 
>> OK. I see now that it DOES work. The '&' give me back the prompt.
>> 
>> The thing that was confusing me is that pesky percent complete output that
>> keeps getting sent to the screen. Any way to shut that off?
> 
> No. There probably should be, though.
> 
> It would be simple enough to add an environment variable to disable
> percent output altogether. It would be better to standardise this so
> that it would disable all unnecessary output; the obvious approach
> would be to have it disable G_message() as well, and migrate modules
> to use G_message() instead of [f]printf().
> 
> -- 
> Glynn Clements <glynn at gclements.plus.com>