Hamish wrote: > For GRASS_HTML_BROWSER, it is read in a number of contexts by e.g. > by g.manual shell script (6.x), g.manual python (7.x), wxGUI, > tcl/tk GUI, grass-run.bat, gui startups, ... > > so it needs to be both cross-platform, cross-language, and cross- > environment (msys vs dos). thus IMO the only portable solution will > be to store it in the OS's native FS format and have each client > code translate downstream as needed rather than guess that up > front.
That's all well and good, but we still aren't making any progress on the original question, i.e. what must the specified program accept as an argument? Until that's know, developers don't know how to use it, and users don't know how to set it. > I find msys to be too large complex to simply say "msys does or > does not support this or that" as a blanket statement. By "MSys", I mean the port of bash. -- Glynn Clements <gl...@gclements.plus.com> _______________________________________________ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
