Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: [4.0.2 bug] commands not written to history
- X-seq: zsh-users 3987
- From: Vincent Lefevre <vincent@xxxxxxxxxx>
- To: zsh-users@xxxxxxxxxx
- Subject: Re: [4.0.2 bug] commands not written to history
- Date: Mon, 2 Jul 2001 12:42:44 +0200
- In-reply-to: <1010630160614.ZM21128@xxxxxxxxxxxxxxxxxxxxxxx>
- Mail-followup-to: zsh-users@xxxxxxxxxx
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <20010629163348.A9632@xxxxxxxxxxxxxx> <1010629155017.ZM14989@xxxxxxxxxxxxxxxxxxxxxxx> <4a9256987fvincent@xxxxxxxxxx> <1010630160614.ZM21128@xxxxxxxxxxxxxxxxxxxxxxx>
On Sat, Jun 30, 2001 at 16:06:14 +0000, Bart Schaefer wrote:
> } BTW, I use NFS, but all the shells were on the same machine.
>
> NFS could be a factor even if only one client machine is involved.
Having had several problems(*) due to NFS (with 1 client), this could
be the case... Is there a way to lock the history file when something
is written to it?
(*) rm -r sometimes returns a strange error, emacs can't be compiled.
--
Vincent Lefèvre <vincent@xxxxxxxxxx> - Web: <http://www.vinc17.org/> - 100%
validated HTML - Acorn Risc PC, Yellow Pig 17, Championnat International des
Jeux Mathématiques et Logiques, TETRHEX, etc.
Work: CR INRIA - computer arithmetic / SPACES project at LORIA
Messages sorted by:
Reverse Date,
Date,
Thread,
Author