[GRASS-dev] gis.m error for i.points (guarantee_xmon exec as string not list?)

[Michael Barton]

This was difficult to track down, but I got it. Glynn updated grass-run.sh
by adding "" around an expression parser and I removed 'eval' from an
expression parser (term procedure) for modules requiring an xterm in
runandoutput.tcl.

Doing one or the other of these was good. Doing both was a gotcha. Since the
term procedure is much more limited in effects (and I pretty much can tell
what is is affecting, I reverted term back to using eval. It all seems to
work OK now.

This probably fixed some other anomalous bugs in some menu items from the
GUI.

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: Fri, 21 Jul 2006 00:09:56 +1200
> To: grass5 <grass-dev at grass.itc.it>
> Subject: [GRASS-dev] gis.m error for i.points (guarantee_xmon exec as string
> not list?)
> 
> Hi,
> 
> in gis.m, Image -> Rectify & georef image group -> set GCPs (both flavors)
> 
> Error: couldn't execute "d.mon start=x0": no such file or directory
> 
> couldn't execute "d.mon start=x0": no such file or directory
> couldn't execute "d.mon start=x0": no such file or directory
>     while executing
> "exec -- $cmd $args &"
>     (procedure "spawn" line 2)
>     invoked from within
> "spawn "d.mon start=$xmon""
>     (procedure "guarantee_xmon" line 15)
>     invoked from within
> "guarantee_xmon"
>     invoked from within
> ".tearoff1 invoke active"
>     ("uplevel" body line 1)
>     invoked from within
> "uplevel #0 [list $w invoke active]"
>     (procedure "tk::MenuInvoke" line 47)
>     invoked from within
> "tk::MenuInvoke .tearoff1 1"
>     (command bound to event)
> 
> 
> 
> I guess "d.mon start=x0" in guarantee_xmon is being exec'd as a string
> and not a list? This was working 2 weeks ago.
> 
> 
> thanks,
> Hamish
> 
>