[GRASS-dev] [GRASS GIS] #2572: grass command welcomes batch job and requires user input

GRASS GIS trac at osgeo.org
Tue Feb 3 12:07:05 PST 2015


#2572: grass command welcomes batch job and requires user input
-----------------------------------------------------+----------------------
 Reporter:  wenzeslaus                               |       Owner:  grass-dev@…              
     Type:  defect                                   |      Status:  new                      
 Priority:  minor                                    |   Milestone:  6.4.5                    
Component:  Startup                                  |     Version:  6.4.4                    
 Keywords:  GRASS_BATCH_JOB, rc file, init, startup  |    Platform:  Linux                    
      Cpu:  Unspecified                              |  
-----------------------------------------------------+----------------------
Changes (by wenzeslaus):

  * keywords:  GRASS_BATCH_JOB, rc file, init => GRASS_BATCH_JOB, rc file,
               init, startup


Comment:

 Fixed in r64438 for 6.4 and in r64408 for trunk.

 r64438 uses does not show the message and does not require the input when
 `GRASS_BATCH_JOB` is defined but still
 [source:grass/branches/releasebranch_6_4/lib/init/init.sh?rev=64438#L437
 creates the rc file]. r64408 removes the message and the request of input
 altogether and leaves just the
 [source:grass/trunk/lib/init/grass.py?rev=64408#L502 creation of the rc
 file].

 r64438 can be tested and was tested using the steps described earlier (and
 by standard start of GRASS after `rm ~/.grassrc6`). Note that to test
 r64408 for version 7, you have to delete (or rename) file `~/.grass7/rc`.

 r64408 should be safe enough to be backported any time to release branch
 but the right time is after RC2 considering the freeze.

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/2572#comment:1>
GRASS GIS <http://grass.osgeo.org>



More information about the grass-dev mailing list