Perhaps you have added it after the call to Init.sh? It needs to be set before Init.sh is run in order to be picked up.
My grass64 is like this now: trap "echo 'User break!' ; exit" 2 3 9 15 GRASS_ADDON_PATH=/usr/local/myproj export GRASS_ADDON_PATH # Set the GISBASE variable GISBASE=/usr/local/grass-6.4.0svn export GISBASE exec "$GISBASE/etc/Init.sh" "$@" So it's defined before Init.sh. If I do echo "$GRASS_ADDON_PATH it appears in GRASS so it's parsed inside grass. Regarding your suggestion: sudo GRASS_ADDON_PATH=/usr/local/myproject grass64 -wxpython I got the same result. An Error Window and the same command-output error. Again, I think this might be an error associated with g.parse since he recognize that the script exists but he is not building Form and he is runned automatically when I insert its name in the command line Regarding your .profile suggestion, what is necessary to be in that .profile file? and where should it be? Franz > Even easier though, would be to set it in your .profile file in your home > directory (create it if it's not there) - then it will always be set > whenever you start a new shell and there is no need to edit the GRASS > startup script. If you upgrade to a newer version of GRASS you won't need to > re-edit the startup script either. Or you could just specify it on the > command-line before starting GRASS; something like: > p...@haptimap:~/gis$ GRASS_ADDON_PATH=/usr/local/myproject grass64 > should also work. > > Best regards > > Paul >
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
