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
HISTFILE=myhist2
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).
On Tue, 1 Jun 2004 15:14:35 +0200 Radim Blazek <blazek@itc.it> wrote:
I have also fixed the 'magic' bug in attributes form (update mode did
non work). It was most probably caused by GRASS_FORM_MODE variable
which I replaced by'-e' flag in d.what.vect. d.m global option moved
to vector's options. d.what.vect will from now by default use VIEW
mode.
Is there an option to set the default mode to EDIT, e.g. with a alias?
If so, where is the appropriated place to put this alias or is there
probably another option to set EDIT to the default vector option?
> I have also fixed the 'magic' bug in attributes form (update mode did
> non work). It was most probably caused by GRASS_FORM_MODE variable
> which I replaced by'-e' flag in d.what.vect. d.m global option moved
> to vector's options. d.what.vect will from now by default use VIEW
> mode.
Is there an option to set the default mode to EDIT, e.g. with a alias?
If so, where is the appropriated place to put this alias or is there
probably another option to set EDIT to the default vector option?