[GRASS-dev] GRASS startup behaviour on Win differs from Unix

GRASS GRASS developer
1

Hi all,

when I start GRASS from a Linux shell, going through Init.sh,
I can supply the name of a mapset and GRASS will automatically
log into that.

When I do the same in Windows, from cmd.exe and going through
Init.bat, I always get the interactive login screen. Is that
intented behaviour? Or is there something I am doing wrong with
the mapset path specification?

Linux:

grass64 $HOME/grassdb/test/usr

-> logs straight into mapset

Win:

grass64.bat c:\grassdb\test\user

-> goes to interactive login

Cheers,

Ben

------
Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information.

2

In answer to myself:

Init.sh has this:

  # User selects LOCATION and MAPSET if not set
  if [ ! "$LOCATION" ] ; then

      [...]

    # Check for text interface
    text)
      "$ETC/set_data"

Whereas Init.bat just does:

  :text

  "%WINGISBASE%\etc\set_data"

So it will always go to the interactive login,
no matter if $LOCATION is already set or not.

Wouldn't it be a good idea to have both scripts
behave identically?

Ben

----- Original Message -----

Hi all,

when I start GRASS from a Linux shell, going through Init.sh,
I can supply the name of a mapset and GRASS will automatically
log into that.

When I do the same in Windows, from cmd.exe and going through
Init.bat, I always get the interactive login screen. Is that
intented behaviour? Or is there something I am doing wrong with
the mapset path specification?

Linux:

grass64 $HOME/grassdb/test/usr

-> logs straight into mapset

Win:

grass64.bat c:\grassdb\test\user

-> goes to interactive login

Cheers,

Ben

------
Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information.