[GRASS-dev] Re: v.digit does not start from gis.m

[Glynn Clements]

Maris Nartiss wrote:

> Your idea works like charm. Attached it as patch for faster commiting.

Hmm. Do we always want to discard the output?

"spawn" will send the output to gis.m's stdout/stderr (e.g. the
terminal), similar to using:

	exec d.mon start=$xmon >@stdout 2>@stderr

However, explicitly redirecting in this way can be problematic on
Windows, apparently.

I have no preference either way, but we should probably see if anyone
else does.

> Only thing that makes me wonder - that "spawn" call was there since
> May 8 2006 [1] - why it was problem only for 6.3? Or noone was using
> ever v.digit from gis.m??

The problem is timing-dependent. If the monitor is already running,
there won't be a problem. If the monitor manages to initialise before
v.digit gets around to connecting to it, there won't be a problem.

It's possible that recent changes to the display architecture have
affected the timing in some way.

In any case, waiting for d.mon to complete is The Right Thing so far
as guarantee_xmon is concerned, IMHO.

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