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

[Markus Neteler]

On Fri, Feb 7, 2014 at 5:49 PM, Glynn Clements <glynn at gclements.plus.com> wrote:
>
> 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).

This is hardly feasible for the majority of the users. Perhaps I don't
understand the suggestion, at least for Windows OS users (nad most
Linux/Mac newcomers).

Markus