...and any script on my desktop or in my documents folder
would be accessible to g.parser and GRASS. (Note: I'm not
sure if ";" or something else should be the separator
between paths). This is very convenient for having a
permanent folder outside the main GRASS distribution
location where you can put any custom scripts.
does that really work??
it should be an environment variable, not a g.gisenv GRASS variable.
the path separator on UNIXes is ':', the path sep on MS Win is ';'.
but those shouldn't be needed here (unless you want to define
multiple addon dirs).
It really does work. It's pretty nice. I don't know how .grassrc6 handles separators--GRASS specific or OS specific.
Michael
______________________________
C. Michael Barton, Professor of Anthropology
Director of Graduate Studies, School of Human Evolution & Social Change
Director, Center for Social Dynamics & Complexity
Arizona State University
Tempe, AZ 85287-2402
USA
...and any script on my desktop or in my documents folder
would be accessible to g.parser and GRASS. (Note: I'm not
sure if ";" or something else should be the separator
between paths). This is very convenient for having a
permanent folder outside the main GRASS distribution
location where you can put any custom scripts.
does that really work??
it should be an environment variable, not a g.gisenv GRASS variable.
the path separator on UNIXes is ':', the path sep on MS Win is ';'.
but those shouldn't be needed here (unless you want to define
multiple addon dirs).
Hello all
Thanks for your good advice. I decided to go with the option of
EXPORTing the grass addon path and put my scripts there, which works
ok, well... kind of.
It happens that when I launch GRASS from the terminal, the
GRASS_ADDON_PATH gets correctly added to the PATH and I can load my
test script. However, if I start GRASS from the gnome menu (or
gnome-do) the GRASS_ADDON_PATH gets ignored. Maybe theres some config
file that I have to tweak?
On Tue, Jun 30, 2009 at 5:54 PM, Michael Barton<Michael.Barton@asu.edu> wrote:
It really does work. It's pretty nice. I don't know how .grassrc6 handles
separators--GRASS specific or OS specific.
Michael
______________________________
C. Michael Barton, Professor of Anthropology
Director of Graduate Studies, School of Human Evolution & Social Change
Director, Center for Social Dynamics & Complexity
Arizona State University
Tempe, AZ 85287-2402
USA
...and any script on my desktop or in my documents folder
would be accessible to g.parser and GRASS. (Note: I'm not
sure if ";" or something else should be the separator
between paths). This is very convenient for having a
permanent folder outside the main GRASS distribution
location where you can put any custom scripts.
does that really work??
it should be an environment variable, not a g.gisenv GRASS variable.
the path separator on UNIXes is ':', the path sep on MS Win is ';'.
but those shouldn't be needed here (unless you want to define
multiple addon dirs).