[GRASS-dev] [GRASS GIS] #1068: unnecessary error information at GRASS startup

[GRASS GIS]

#1068: unnecessary error information at GRASS startup
----------------------+-----------------------------------------------------
 Reporter:  msieczka  |       Owner:  grass-dev@…              
     Type:  defect    |      Status:  new                      
 Priority:  minor     |   Milestone:  6.4.0                    
Component:  Startup   |     Version:  svn-releasebranch64      
 Keywords:            |    Platform:  All                      
      Cpu:  All       |  
----------------------+-----------------------------------------------------
Changes (by hamish):

  * component:  Default => Startup


Comment:

 If the last-known mapset or location isn't found any more, an error saying
 it isn't found seems entirely appropriate. The expected behaviour (load up
 the last mapset) is not possible, and any time that the expected thing
 isn't going to happen there should be warning bells sounding.

 The thing to worry about, I think, is how well it recovers from that
 situation..

 the current 6.x wxGUI gives this in the terminal if the mapset went away:
 {{{
 ...
 ERROR: MAPSET user1 not found
 ERROR: Mapset <user1> not found
 }}}

 but loads up the loc'n with the list of existing mapsets.

 If the loc'n is no longer there the wxGUI startup gives you:

 {{{
 Cleaning up temporary files ...
 Starting GRASS ...
 access: No such file or directory
 ERROR: LOCATION << /path/to/old/name >> not available
 }}}

 then loads up the GISDBASE dir and selects the first loc'n there.


 The -text version gives this after esc-enter, then asks if you want to
 create it.
 {{{
 Mapset <<user1>> is not available
 }}}

 For an invalid loc'n it is similar: asks if you wish to create a new loc'n
 by that name.


 it all seems ok to me.


 Hamish

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/1068#comment:3>
GRASS GIS <http://grass.osgeo.org>