zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: HIST_SAVE_BY_COPY (was Re: The HIST_EXPIRE_DUPS_FIRST might corrupt and wipe partially history file)
Date: Sun, 19 Mar 2023 09:56:39 -0700	[thread overview]
Message-ID: <CAH+w=7Z0O8BTLg8_xfZ3U-XrKdF5RrrC3bFHgXppss5oSTFcZQ@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7Y6BDXBf1mtOMaceTfs7ioL7z+-EycAF8ppWFv-6_arNg@mail.gmail.com>

On Sun, Mar 19, 2023 at 9:53 AM Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> 2) The locking mechanism doesn't work for some other reason.  Make
> sure the HIST_SAVE_BY_COPY option is set (it's the default but check
> anyway).

Is there a reason that HIST_SAVE_BY_COPY uses ${HISTFILE}.new rather
than creating a more uniquely generated name for the copy?


           reply	other threads:[~2023-03-19 16:57 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAH+w=7Y6BDXBf1mtOMaceTfs7ioL7z+-EycAF8ppWFv-6_arNg@mail.gmail.com>]

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='CAH+w=7Z0O8BTLg8_xfZ3U-XrKdF5RrrC3bFHgXppss5oSTFcZQ@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.org \
    /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).