Opened 3 years ago

Last modified 15 months ago

#3258 new enhancement

Launching in text mode should not automaticly use location/mapset from rc file

Reported by: marisn Owned by: grass-dev@…
Priority: normal Milestone: 8.0.0
Component: Startup Version: svn-trunk
Keywords: init rcfile gisrc Cc:
CPU: Unspecified Platform: Unspecified

Description

I am using GRASS on my box in two modes - GUI when I'm on-site and text when remote. This has shown a problem in current rc file logic:

  • If location/mapset has been removed and it is provided during startup, it sill generates an error message of missing location/mapset (took some time till I understood why my batch processing is so verbose)
  • If I have started with -text, subsequent runs will automatically start in text mode with last used location/mapset. If I run GRASS from menu not CLI, it is quite confusing to get thrown directly into some kind of session without choosing one.

GRASS should not start if no location/mapset is specified as rc file could be already outdated. Explicit is always better than implicit. rc should be a hint not a rule, as users are not asked to "use the same location/mapset next time" when it is created.

Change History (6)

comment:1 Changed 3 years ago by mlennert

I wouldn't classify this as a defect. This was a design decision and personally, I actually like the way it works. It requires a bit of getting used to, but then it is quite nice.

comment:2 Changed 3 years ago by martinl

Milestone: 7.2.17.2.2

comment:3 Changed 2 years ago by neteler

Milestone: 7.2.27.2.3

Ticket retargeted after milestone closed

comment:4 Changed 22 months ago by martinl

Milestone: 7.2.37.4.1
Type: defectenhancement

comment:5 Changed 18 months ago by neteler

Milestone: 7.4.17.4.2

comment:6 Changed 15 months ago by wenzeslaus

Keywords: init rcfile gisrc added
Milestone: 7.4.28.0.0

This would be a change in behavior so 8.0, but perhaps the batch processing should not lead to the rc file in home being updated and should not use the rc file. Is that the problem?

Note: See TracTickets for help on using tickets.