On Mon, 2010-03-08 at 01:20 +0100, Nikos Alexandris wrote:
I understand that this way of using grass isn't recommended for (let
us say) beginners. Nevertheless, my aim was/is to put most of this
thread in a wiki-page because I consider it as very practical.
--%---
Nikos Alexandris wrote:
Is there a way to lock-out all
other versions of grass-modules from being detectable when I am already
inside a grass70 session?
Glynn:
The grassXY scripts prepend the GRASS directories to PATH,
LD_LIBRARY_PATH, etc. They won't remove any entries which are
Nikos Alexandris wrote:
Is there a way to lock-out all
other versions of grass-modules from being detectable when I am already
inside a grass70 session?
Glynn Clements wrote:
The grassXY scripts prepend the GRASS directories to PATH,
LD_LIBRARY_PATH, etc. They won't remove any
Glynn,
thank you so much for sharing :-)
I understand that this way of using grass isn't recommended for (let
us say) beginners. Nevertheless, my aim was/is to put most of this
thread in a wiki-page because I consider it as very practical.
Before doing so I want to test more to look for gaps and
Nikos wrote:
So, when working on a project, it is best practice to stick
with grass-sessions?
There will be a number of opinions on this, and there are probably a number
of valid answers depending on the use-case and expertise level of the user.
Mine is that it is useful to use init.sh
Nikos wrote:
So, when working on a project, it is best practice to stick
with grass-sessions?
Hamish wrote:
There will be a number of opinions on this, and there are probably a number
of valid answers depending on the use-case and expertise level of the user.
( ...I guess there is no thing
Nikos Alexandris wrote:
The thing that troubles me most currently is: using normal grass
sessions you get entries recorded in
/grassdb/location/mapset/.bash_history while working with pure bash
shell entries go in ~/.bash_history.
- Merging existing grass-bash_history(-ies) with
Νίκος:
Is there a way to lock-out all
other versions of grass-modules from being detectable when I am already
inside a grass70 session?
Glynn:
The grassXY scripts prepend the GRASS directories to PATH,
LD_LIBRARY_PATH, etc. They won't remove any entries which are already
there.
I only
Nikos Alexandris wrote:
The thing that troubles me most currently is: using normal grass
sessions you get entries recorded in
/grassdb/location/mapset/.bash_history while working with pure bash
shell entries go in ~/.bash_history.
- Merging existing grass-bash_history(-ies) with
Apologies for a second post with the code. Just to make it easier to
read/ understand what I've changed.
Νίκος Αλεξανδρής wrote:
Is there a way to lock-out all other versions of grass-modules from
being detectable when I am already inside a grass70 session?
Glynn Clements wrote:
The
Hi Glynn!
I've set-up my system based on your detailed descriptions/instructions
below (old post) using grass64.
1. Would you mind sharing in addition the way you change between
mapsets/locations? Do you start a new shell session after re-defining
somehow the variables LOCATION_NAME or/and
Νίκος Αλεξανδρής wrote:
I've set-up my system based on your detailed descriptions/instructions
below (old post) using grass64.
1. Would you mind sharing in addition the way you change between
mapsets/locations? Do you start a new shell session after re-defining
somehow the variables
Dear friends,
I can run some simple scripts on python if I start
Msys - grass64 - python myscrypt.py
But now I would like to know if I can build a python
code outside of a msys/grass session, and get
access on a mapset withour stay running grass.
thanks a lot,
milton
Milton Cezar Ribeiro wrote:
I can run some simple scripts on python if I start
Msys - grass64 - python myscrypt.py
But now I would like to know if I can build a python
code outside of a msys/grass session, and get
access on a mapset withour stay running grass.
The GRASS libraries require
14 matches
Mail list logo
