[GRASS-dev] [GRASS GIS] #3573: Save current working directory in wxGUI workspace and use it

GRASS GIS trac at osgeo.org
Thu Jun 7 01:05:02 PDT 2018


#3573: Save current working directory in wxGUI workspace and use it
--------------------------+-----------------------------------------------
  Reporter:  wenzeslaus   |      Owner:  grass-dev@…
      Type:  enhancement  |     Status:  new
  Priority:  normal       |  Milestone:  8.0.0
 Component:  Startup      |    Version:  unspecified
Resolution:               |   Keywords:  workspace, recent, startup, wxGUI
       CPU:  Unspecified  |   Platform:  Unspecified
--------------------------+-----------------------------------------------

Comment (by mlennert):

 Replying to [comment:2 wenzeslaus]:
 > Replying to [comment:1 mlennert]:
 > > I have to admin that I never even noticed that we had this option.
 >
 > Accessible from Setting or using cd command in the Console tab (you
 basically get some consistency between terminal and Console tab).

 I don't know what you mean by consistency, but when I cd in the console
 this (obviously) has no impact on the terminal pwd.

 >
 > > I find this a bit weird, first of all because I don't know what the
 "current working directory" actually means in GRASS GIS?
 >
 > It means just the same thing it means in the command line. Every program
 has current working directory (or whatever we want to call it). `cd` and
 `$PWD` or `pwd` in Linux command line, `os.getcwd()` and `os.chdir()` in
 Python.

 Yes, but here we have to be careful to be clear that when we say
 "program", we mean the GUI, not any GRASS module launched from anywhere.

 >
 > > In the GUI I understand it to mean the directory that is opened by
 default in any file system widgets.
 >
 > Right. (At least that's how it works on Linux.) I usually forget about
 this behavior. This might be nice for some users and strange (but not
 necessarily confusing) to some others.

 It is very nice, as I've had situations where I had to save multiple image
 versions of the GUI screen into one directory and had to navigate to that
 directory each time. Now I know that I can cd into that directory in the
 console and thus make it the GUI's pwd. :-)

 > > Does it have any other effect?
 >
 > You can put all your files for import and all color tables for one
 project into one directory (and perhaps subdirs) and then just cd there
 and you don't need to use full path just a relative one. I guess that's
 clear, but the point is that it applies for terminal as well as the GUI
 Console tab.

 I don't know what you mean by "it applies" ? How ? IIUC your ticket, you
 are pleading for that it should ? But this would only be for the situation
 where the pwd is stored in a workspace, or ?

 >It is also advantageous when people are following commands in a list of
 instructions - you need to deal with specifying the path just once (and
 the exported files will be in the directory set at the beginning).

 But you have to be very careful to make sure that all commands are
 executed either only in the console/GUI or only in the terminal...

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/3573#comment:4>
GRASS GIS <https://grass.osgeo.org>



More information about the grass-dev mailing list