[GRASS-dev] running commands in background

[Michael Barton]

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?

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: Hamish <hamish_nospam at yahoo.com>
> Date: Thu, 25 May 2006 18:19:06 +1200
> To: Michael Barton <michael.barton at asu.edu>
> Cc: <grass-dev at grass.itc.it>
> Subject: Re: [GRASS-dev] running commands in background
> 
>> I know that if you launch a command by only typing the command name
>> (no arguments) followed by Œ&¹, you can get the command gui to launch
>> modally. Then this command can process while you launch another
>> command.
>> 
>> Is there any way to get a command launched from the command line
>> (i.e., with arguments) to run in the background so that you can launch
>> another command from the command prompt?
>> 
>> I¹ve tried... 
>> 
>> [command] [arguments] &
>> r.what input=precip_9400 east_north=749204,3614262 &
>> 
>> and this doesn¹t seem to work.
> 
> It proably did, just hit enter a bunch of times as the prompt is getting
> clobbered by the first module's output? (redirect output?)
> 
> GRASS> g.command [arguments]
> ^Z
> GRASS> bg
> 
> is another way.
> 
> 
> 
> Hamish