[GRASS-dev] Handling of Python scripts on MS Windows

Glynn Clements glynn at gclements.plus.com
Fri Feb 7 08:49:32 PST 2014


Markus Neteler wrote:

> > It's fairly trivial to set a valid GRASS environment globally, so that
> > commands are usable in any shell. That's how I've had it on Linux
> > since roughly forever; I don't run the grass70 script unless I'm
> > testing it.
> >
> > FWIW, I want to make that the default mode of operation.
> 
> Could you please elaborate? Say, what would be the difference to the
> current way?

The difference is that you don't "start" GRASS. You set the required
environment variables from e.g. ~/.profile so that GRASS commands work
in any shell (or via any other execution mechanism, e.g. M-! from
within Emacs).

-- 
Glynn Clements <glynn at gclements.plus.com>


More information about the grass-dev mailing list