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

Re: The HIST_EXPIRE_DUPS_FIRST might corrupt and wipe partially history file if many shells exit at the same time

X-seq: zsh-users 28975
From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
To: Piotr Karbowski <piotr.karbowski@xxxxxxxxxxxxx>
Cc: zsh-users@xxxxxxx
Subject: Re: The HIST_EXPIRE_DUPS_FIRST might corrupt and wipe partially history file if many shells exit at the same time
Date: Sun, 19 Mar 2023 14:01:17 -0700
Archived-at: <https://zsh.org/users/28975>
In-reply-to: <b821265f-c8e4-90e2-4f78-4a6cc98ae8b1@protonmail.ch>
List-id: <zsh-users.zsh.org>
References: <33a75d10-d765-3d79-a179-943c57659111@protonmail.ch> <CAH+w=7Y6BDXBf1mtOMaceTfs7ioL7z+-EycAF8ppWFv-6_arNg@mail.gmail.com> <b821265f-c8e4-90e2-4f78-4a6cc98ae8b1@protonmail.ch>

On Sun, Mar 19, 2023 at 11:38 AM Piotr Karbowski
<piotr.karbowski@xxxxxxxxxxxxx> wrote:
>
> The HIST_SAVE_BY_COPY does not seems to be enabled and I am unable to
> enable it.

"setopt" with no arguments shows you only the options that differ from
the defaults.  So if HIST_SAVE_BY_COPY does not show up, it IS
enabled.

Use "set -o" (with no other arguments) to see the full set of options
and on/off status, or "setopt kshoptionprint" before running "setopt"
alone.

If an option shows up with a  "no" prefix in unsetopt output, that
means it is on.  There is no third state.

Follow-Ups:
- Re: The HIST_EXPIRE_DUPS_FIRST might corrupt and wipe partially history file if many shells exit at the same time
  - From: Piotr Karbowski

References:
- The HIST_EXPIRE_DUPS_FIRST might corrupt and wipe partially history file if many shells exit at the same time
  - From: Piotr Karbowski
- Re: The HIST_EXPIRE_DUPS_FIRST might corrupt and wipe partially history file if many shells exit at the same time
  - From: Bart Schaefer
- Re: The HIST_EXPIRE_DUPS_FIRST might corrupt and wipe partially history file if many shells exit at the same time
  - From: Piotr Karbowski

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