[GRASS-dev] hardcoded 'xterm': wrapper?

Hamish hamish_nospam at yahoo.com
Mon Aug 28 06:21:38 EDT 2006


Michael Barton wrote:
> Where are hard-coded xterm references causing a problem? Is it only in
> the GUI or is it elsewhere?


$ cd grass63-src/
$ grep -rI xterm *

debian/control:Depends: ${shlibs:Depends}, xterm, libgrass
debian/changelog:    - depend on xterm
gem/main.c:     - a simple wrapper g.install with GRASS style parameters. Should start an xterm and ask for su pwd,
gui/tcltk/gis.m/runandoutput.tcl:       set runxterm [button $cmdpane.xterm -text [G_msg "Run in Xterm"] -command "$gronsole run_xte     \[string trim \[$cmdtext get 1.0 end\]\] {}"]
gui/tcltk/gis.m/runandoutput.tcl:       pack $runbutton $run2button $runuibutton $runxterm \
gui/tcltk/gis.m/runandoutput.tcl:       $gronsole run_xterm $cmd gism
gui/tcltk/gis.m/runandoutput.tcl:       eval [list exec -- xterm -name xterm-grass -e $env(GISBASE)/etc/grass-run.sh $cmd] $args &
gui/tcltk/gis.m/script/r.support.sh:eval `exec xterm -e r.support map=$GIS_OPT_INPUT`
gui/tcltk/gis.m/script/r.reclass.rules:exec xterm -e "$GISBASE/etc/grass-run.sh" r.reclass "input=$GIS_OPT_INPUT" "output=$GIS_OPT_O    PUT"
gui/tcltk/gis.m/script/d.colors.sh:# PURPOSE:       Make xterm module d.colors useable from the GUI
gui/tcltk/gis.m/script/d.colors.sh:exec xterm -e "$GISBASE/etc/grass-run.sh" d.colors "map=$GIS_OPT_INPUT"
gui/tcltk/gis.m/script/r.colors.rules:exec xterm -e "$GISBASE/etc/grass-run.sh" r.colors "map=$GIS_OPT_INPUT" color=rules
gui/tcltk/gis.m/script/r.recode.rules:exec xterm -e "$GISBASE/etc/grass-run.sh" r.recode "input=$GIS_OPT_INPUT" "output=$GIS_OPT_OUT    T"
gui/tcltk/gis.m/script/d.text.sh:exec xterm -e "$GISBASE/etc/grass-run.sh" $cmd
gui/tcltk/d.m/vector.tcl:       exec xterm -bg $bgcolor -title "$mapname columns" \
gui/tcltk/d.m/vector.tcl:       exec xterm -bg $bgcolor -title "$mapname data" \
gui/tcltk/d.m/thematic.tcl:     exec xterm -bg $bgcolor -title "$mapname columns" \
gui/tcltk/d.m/thematic.tcl:     exec xterm -bg $bgcolor -title "$mapname data" \
gui/tcltk/d.m/script/r.support.sh:eval `exec xterm -e r.support map=$GIS_OPT_INPUT`
gui/tcltk/d.m/script/r.reclass.rules:eval `exec xterm -e r.reclass input=$GIS_OPT_INPUT output=$GIS_OPT_OUTPUT`
gui/tcltk/d.m/script/d.colors.sh:# PURPOSE:         Make xterm module d.colors useable from the GUI
gui/tcltk/d.m/script/d.colors.sh:eval `exec xterm -e d.colors map=$GIS_OPT_INPUT`
gui/tcltk/d.m/script/r.colors.rules:eval `exec xterm -e r.colors map=$GIS_OPT_INPUT color=rules`
gui/tcltk/d.m/script/r.recode.rules:eval `exec xterm -e r.recode input=$GIS_OPT_INPUT output=$GIS_OPT_OUTPUT` 
gui/tcltk/d.m/script/d.text.sh:eval `exec xterm -e $cmd`
gui/tcltk/d.m/d.m.tcl:    eval exec -- xterm -name xterm-grass -e $env(GISBASE)/etc/grass-run.sh $cmd &
gui/tcltk/d.m/d.m.tcl:    eval exec -- xterm -name xterm-grass -e $env(GISBASE)/etc/grass-run.sh $cmd $args &
gui/tcltk/d.m/chart.tcl:        exec xterm -bg $bgcolor -title "$mapname columns" \
gui/wxpython/scripts/r.support.sh:eval `exec xterm -e r.support map=$GIS_OPT_INPUT`
gui/wxpython/scripts/r.reclass.rules:exec xterm -e "$GISBASE/etc/grass-run.sh" r.reclass "input=$GIS_OPT_INPUT" "output=$GIS_OPT_OUT    T"
gui/wxpython/scripts/r.colors.rules:exec xterm -e "$GISBASE/etc/grass-run.sh" r.colors "map=$GIS_OPT_INPUT" color=rules
gui/wxpython/scripts/r.recode.rules:exec xterm -e "$GISBASE/etc/grass-run.sh" r.recode "input=$GIS_OPT_INPUT" "output=$GIS_OPT_OUTPU
lib/init/epsg_option.tcl.in:                                            exec -- xterm -e $env(GISBASE)/etc/make_location_epsg.sh \
lib/init/grass-run.src:if [ "$TERM" = "xterm" ] ; then
lib/init/grass-run.src:# workaround for systems with xterm is setuid/setgid
lib/vask/README:happen with xterm, which has many configuration options which impact
lib/vask/V_init.c:    system("clear");  /* this is a kludge - xterm has problems
lib/gtcltk/gronsole.tcl:proc Gronsole::run_xterm {path cmd tags} {
lib/gtcltk/gronsole.tcl:        Gronsole::annotate $path $cmd [concat xterm $tags]
lib/gtcltk/gronsole.tcl:        exec -- xterm -name xterm-grass -e $env(GISBASE)/etc/grass-run.sh $cmd &
lib/external/bwidget/entry.tcl:            $path:cmd configure -cursor xterm
scripts/r.mapcalculator/r.mapcalculator:        exec xterm -e r.mapcalc &
scripts/r3.mapcalculator/r3.mapcalculator:      exec xterm -e r3.mapcalc &


Hamish




More information about the grass-dev mailing list