[GRASS-dev] Re: winGRASS

[Michael Barton]

As best I can tell, g.manual [module name] simply calls whatever browser has
been set in the environmental variable GRASS_HTML_BROWSER. It seems like a C
shortcut to using TclTk code to do the same thing.

$pgm_name is simply a variable to store the name of the current module
(d.rast, d.vect, etc.)


The TclTk code below executes whatever is stored in GRASS_HTML_BROWSER to
open the doc file stored at [module name].html.

g.manual shouldn't need a bash environment any more than any other GRASS
command.

If there are problems with the help buttons on the GUI options panels and
not on the module dialogs, I think more likely, it is a problem with the
"run" procedure used in the options panels to launch g.manual. Look at
raster.tcl and change how it starts in a couple ways. Try "spawn" instead of
"run". Also try the solution I mentioned with the execute procedure and the
devnull variable.

Michael


On 2/12/07 5:14 PM, "Moritz Lennert" <mlennert at club.worldonline.be> wrote:

>> Another interesting point is that in lib/gis/gui.tcl the help button runs:
>> exec $env(GRASS_HTML_BROWSER) $env(GISBASE)/docs/html/$pgm_name.html &
>> whereas most places in gis.m run g.manual $pgm_name or something similar.
>> As g.manual requires a bash interpreter to run, maybe the former solution
>> is more platform-independent? Or are other places not supposed to access
>> $GRASS_HTML_BROWSER - should it be just for g.manual to use?
>> 
> 
> Maybe Michael or Glynn can help us with this ?
> 
> Moritz

__________________________________________
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