[GRASS-dev] g.parser: Note on setting bash' IFS to parse separate identities
Paulo van Breugel
p.vanbreugel at gmail.com
Tue Nov 4 05:14:51 PST 2014
On Tue, Nov 4, 2014 at 1:58 PM, Glynn Clements <glynn at gclements.plus.com>
> Nikos Alexandris wrote:
> > --%<---
> > ...individual comma separated identities for an option named "input"
> > can be parsed with the following Bash shell code:
> > IFS=,
> > for opt in $GIS_OPT_INPUT ; do
> > ... "$opt"
> > done
> > --->%--
> > Doesn't this require to set the IFS back to what it was? Maybe note it
> > too?
> Or even just remove the reference to bash from the 7.x documentation.
> If you're using 7.x, Python is almost mandatory, so why would you
> write bash scripts?
In what sense mandatory? I see it to be highly desirable, especially if you
want to share your scripts. But not everybody is well versed in python, and
the option to write bash scripts will remain useful I am sure to part of
the users. Why not maintaining some useful references?
> Glynn Clements <glynn at gclements.plus.com>
> grass-dev mailing list
> grass-dev at lists.osgeo.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the grass-dev