[GRASS-user] can I access mapset outside of grass, by using python?

Glynn Clements glynn at gclements.plus.com
Sun Mar 7 21:42:41 EST 2010

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 "bash_history" would
> probably be NOT a good idea.
> - Trying to separate (somehow) grass-commands history-entries and other
> shell actions related to a specific grass-project (speak
> grassdb/project/location/mapset) from other grass-projects or
> non-grass-projects is, I think, non-sense.
> So, when working on a project, it is best practice to stick with
> grass-sessions?

You can control where history entries are written via $HISTFILE and
the "history" command. It's up to the user how they want to manage
their shell history.

Glynn Clements <glynn at gclements.plus.com>

More information about the grass-user mailing list