[GRASS-dev] cvs gis.m error

[Glynn Clements]

Trevor Wiens wrote:

> > I'm running Lorenzo's binaries of 27 May with no problems in general. Check
> > in gronconsole to see if there are any errors reported there.
> 
> It simply shows that the command d.mon start=gism -s 
> is still running. That's it. Stopping the existing display and opening
> an new one doesn't resolve the problem. No errors, but also no display
> either. 
> 
> When I modify the run command in runandoutput.tcl to stop sending
> everything to /dev/ null, the following happens. The error appears
> sooner with the message No such monitor gism on the command 
> d.mon stop=gism
> 
> with the rest being pretty much as before.
> 
> Hmm....
> 
> BTW, this makes me wonder about the wisdom of sending everything
> to /dev/null. A session log file makes more sense to me. 

That's an option, as is redirecting to gis.m's stderr (typically the
terminal) with "2>@stderr", but you have to redirect stderr somewhere. 
If a command spawned with exec or open writes anything to an
unredirected stderr, Tcl will generate an error.

-- 
Glynn Clements <glynn at gclements.plus.com>