zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk
Subject: Re: revisiting history-file rewriting
Date: Fri, 18 Mar 2005 10:49:08 +0000	[thread overview]
Message-ID: <200503181049.j2IAn96p007683@news01.csr.com> (raw)
In-Reply-To: <20050316204059.GA1298@blorf.net>

Wayne Davison wrote:
> This patch adds the option HIST_OVERWRITE that is off by default.  This
> changes the default history-rewriting strategy to one that uses the name
> $HISTFILE.new for writing out the history lines, and then renaming it
> over $HISTFILE when it is done (both actions happen with the history
> file locked).

How would this change the result when multiple shells exit at once?
I'm not entirely clear how the locking affects the fact that multiple
shells want to rewrite the file in this case.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

**********************************************************************


  parent reply	other threads:[~2005-03-18 10:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-16 20:40 Wayne Davison
2005-03-17  2:09 ` Geoff Wing
2005-03-17  2:49   ` Wayne Davison
2005-03-18 16:18     ` Andrey Borzenkov
2005-03-18 17:51       ` Wayne Davison
2005-03-18 18:02         ` Wayne Davison
2005-03-17 18:03 ` Bart Schaefer
2005-03-18 18:19   ` Wayne Davison
2005-03-18 21:15     ` Bart Schaefer
2005-03-18 21:47       ` Wayne Davison
2005-03-18 10:49 ` Peter Stephenson [this message]
2005-03-18 17:58   ` Wayne Davison
2005-03-18 18:24     ` Peter Stephenson
2005-03-18 22:53 ` Wayne Davison
2005-03-20  1:57   ` Bart Schaefer
2005-03-21 10:39     ` Peter Stephenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200503181049.j2IAn96p007683@news01.csr.com \
    --to=pws@csr.com \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).