Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

HIST_SAVE_BY_COPY (was Re: The HIST_EXPIRE_DUPS_FIRST might corrupt and wipe partially history file)

X-seq: zsh-workers 51587
From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
To: Zsh hackers list <zsh-workers@xxxxxxx>
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
Archived-at: <https://zsh.org/workers/51587>
In-reply-to: <CAH+w=7Y6BDXBf1mtOMaceTfs7ioL7z+-EycAF8ppWFv-6_arNg@mail.gmail.com>
List-id: <zsh-workers.zsh.org>
References: <33a75d10-d765-3d79-a179-943c57659111@protonmail.ch> <CAH+w=7Y6BDXBf1mtOMaceTfs7ioL7z+-EycAF8ppWFv-6_arNg@mail.gmail.com>

On Sun, Mar 19, 2023 at 9:53 AM Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> 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?

Messages sorted by: Reverse Date, Date, Thread, Author