Hola! See? I knew it was a silly question :-P Thank you for your answers!
It works both with sh test.sh and ./test.sh (@Moritz, yes the +x was there) Thanks again! Will send a diff with the example for the manual page. Cheers, Vero 2016-12-06 8:33 GMT+01:00 Moritz Lennert <[email protected]>: > On 05/12/16 23:06, Markus Neteler wrote: > >> On Mon, Dec 5, 2016 at 9:35 PM, Veronica Andreo <[email protected]> >> wrote: >> >>> Hello list, >>> >>> This is maybe a very silly question, but I do not know what I am missing. >>> I'm trying to run a script using the --exec interface but using the >>> following command, I get: >>> >>> grass73svn /home/veroandreo/grassdata/nc_spm_08_grass7/user1/ --exec >>> test.sh >>> >> >> Like this the "test.sh" must be in the current path. >> So: >> - either give the full path (as Moritz wrote) >> - or call it like this: .... --exec sh test.sh >> > > And just to make sure: If you use the full path (or ./test.sh), test.sh > has to have the executable bit set, i.e. chmod +x test.sh. > > Moritz >
_______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
