[GRASS-dev] Re: [GRASS GIS] #1074: $GRASS_BATCH_JOB isn't executed
GRASS GIS
trac at osgeo.org
Fri May 21 01:25:55 EDT 2010
#1074: $GRASS_BATCH_JOB isn't executed
---------------------+------------------------------------------------------
Reporter: martin | Owner: grass-dev at lists.osgeo.org
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Python | Version: svn-trunk
Resolution: | Keywords: startup
Platform: Linux | Cpu: x86-64
---------------------+------------------------------------------------------
Changes (by hamish):
* keywords: => startup
Comment:
One thing I've wanted to see for a long time, and grass7 init.py is a
great opportunity for, is to have better parsing of command line options
than grass 6's init.sh has. Maybe I'm just used to how good G_parser() is
by comparison..
Anyway, it would be great to be able to pass the batch job script filename
as a command line option to init.py instead of having to mess with special
environment variable hacks etc. to get it to work.
thanks,
Hamish
ps- any objections/comments to adding a "startup" component in trac?
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/1074#comment:2>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list