Opened 5 years ago

Last modified 5 years ago

#3959 new enhancement

Interface needs to warn that directory must be created before start

Reported by: jidanni Owned by: grass-dev@…
Priority: trivial Milestone: 7.8.3
Component: Startup Version: unspecified
Keywords: init grass.py default Cc:
CPU: Unspecified Platform: Unspecified

Description

Yes, file:///usr/share/doc/grass-doc/html/helptext.html#-selecting-the-gis-database-directory warns that directories must already exist before starting the program. However, that warning needs also to appear when the user first does

$ grass

At "Grass needs a directory..."

It needs to tell the user to "Quit. Make the directory with mkdir, etc. And start again.

(Since for some reason the program is unable to create directories.)

Change History (3)

comment:1 by wenzeslaus, 5 years ago

Keywords: init grass.py default added

I also prefer if the situation is resolved automatically in general, but I'm not sure if that should be the case in command line startup. The message should suggest next steps, but creating a directory where all user's data is stored (not just some temporary dump directory) might be little too much initiative taken by a command line program because user may expect better control.

When you start GUI, it does create this directory by default, but it will in the future. That's however different from command line I think.

Therefore, I'm for improving the message (perhaps even explaining the purpose of that directory better) but not changing the behavior.

comment:2 by jidanni, 5 years ago

Indeed, with no DISPLAY,

$ grass
Starting GRASS GIS...
WARNING: It appears that the X Windows system is not active.
A graphical based user interface is not supported.
(DISPLAY variable is not set.)
Switching to text based interface mode.

Hit RETURN to continue.


ERROR: Path '/home/dyy/<UNKNOWN>/<UNKNOWN>' doesn't exist
Exiting...

That final "ERROR: Path '/home/dyy/<UNKNOWN>/<UNKNOWN>' doesn't exist" is too abrupt too.

comment:3 by neteler, 5 years ago

Milestone: 7.8.3
Note: See TracTickets for help on using tickets.