[GRASS-dev] Re: MS-Windows native GRASS

[Huidae Cho]

On Mon, Sep 18, 2006 at 11:15:23AM +0100, Glynn Clements wrote:
> 
> Huidae Cho wrote:
> 
> > $env(GRASS_HTML_BROWSER) $env(GISBASE)/docs/html/$pgm_name.html &
> > 
> > So we can define:
> > proc g_manual {pgm} {
> > 	global env
> > 
> > 	exec $env(GRASS_HTML_BROWSER) $env(GISBASE)/docs/html/$pgm.html &
> > }
> > 
> > We need a generic way to call programs including shell scripts and
> > binary files (e.g., sh -c 'cmd args').  Is grass-xterm-wrapper used only
> > for interactive programs or can we use this for non-interactive ones
> > too?
> 
> grass-xterm-wrapper is only used for programs which require a
> terminal. It should not be used for non-interactive programs, as gis.m
> needs to read the process' output.
> 
> > We have a Windows version of grass-xterm-wrapper which can
> > be used in both ways.
> 
> That's a mistake. As the name implies, grass-xterm-wrapper is supposed
> to be a front-end to an xterm-like terminal program. Its sole purpose
> is to allow terminals other than xterm to be used for programs which
> require a terminal. Once we eventually eliminate the need to use a
> terminal, it will go away altogether.
> 

I agree, rxvt may be more suitable for the wrapper. But, curses based
modules (I didn't count how many modules actually depend on this library)
don't work with rxvt and that's why I chose cmd.exe for winGRASS.  For
example, grass -text doesn't work in rxvt.

Huidae