Hi, to test if and when GRASS fails with white space in the data path, I have changed (on my Linux box) "$HOME/grassdata/" to $HOME/grass data/".
Besides a failure in command line startup: grass63 "$HOME/grass data/spearfish60/user1" Cleaning up temporary files..... Starting GRASS ... The LOCATION "neteler" does not exist. Please create first BUT: ls -la "$HOME/grass data/spearfish60/user1" total 112 drwxr-xr-x 16 neteler ssi 4096 Aug 17 18:36 . drwx------ 10 neteler ssi 4096 Aug 6 13:54 .. -rw------- 1 neteler ssi 28956 Aug 17 18:36 .bash_history ... I found that "wxgrass" fails, too. This could be of interest for the MS-Windows portability: GRASS 6.3.cvs (nc_spm_06):~/grassaddons/gui > Sorry <data/nc_spm_06/neteler/.tmp/bartok/15316.2.ppm> is not a valid option Sorry <data/nc_spm_06/neteler/.tmp/bartok/15316.2.pgm> is not a valid option Sorry <data/nc_spm_06/neteler/.tmp/bartok/15316.0> is not a valid option Could not run g.pnmcomp GRASS 6.3.cvs (nc_spm_06):~/grassaddons/gui > g.gisenv GISDBASE=/nfsmnt/ssi0/ssi/neteler/grass data DEBUG=0 MAPSET=neteler LOCATION_NAME=nc_spm_06 GRASS_GUI=text I recommend that (wxgrass) developers also put a white space into their grassdata/ path to easily trap problems like above. Most problems will be trivial quoting issues. Markus ------------------ ITC -> dall'1 marzo 2007 Fondazione Bruno Kessler ITC -> since 1 March 2007 Fondazione Bruno Kessler ------------------ _______________________________________________ grass-dev mailing list [email protected] http://grass.itc.it/mailman/listinfo/grass-dev
