[GRASS5] GRASS 5.7.0 beta1

Glynn Clements glynn.clements at virgin.net
Fri Jun 4 09:24:59 EDT 2004

Radim Blazek wrote:

> On Friday 04 June 2004 00:29, Glynn Clements wrote:
> > And, environment issues aside, you can't make the shell close the
> > history file and start writing a new one. You just have to accept the
> > fact that the history will be stored in the starting mapset.
> In bash it is possible to do
> export  HISTFILE=myhist1
> history -w
> history -r myhist2

OK; but shouldn't that be:

	history -w
	history -r

Presumably, changing HISTFILE will determine where the history is
written upon exit?

> similarly in tcsh it should be possible 
> history -S myhist1
> history -L myhist2
> but it must be in a script without #!/bin/, is it a problem?

Yes; it's the same issue as environment variables.

You would have to have g.mapset (or whatever) emit shell commands,
then use e.g.:

	eval `g.mapset`

Or make g.mapset a script such that you could run:

	source g.mapset

Or make g.mapset spawn a new shell (similar to the way that the newgrp
program works).

Glynn Clements <glynn.clements at virgin.net>

More information about the grass-dev mailing list