From: Bart Schaefer <schaefer@brasslantern.com>
To: dominik.vogt@gmx.de, Zsh Users <zsh-users@zsh.org>
Subject: Re: Bug: Losing .zsh_history
Date: Wed, 5 Oct 2022 15:16:27 -0700 [thread overview]
Message-ID: <CAH+w=7ZrrKqW35H6uX623KOCe7Bx1BJyCiRzc+F=24spHD6=dA@mail.gmail.com> (raw)
In-Reply-To: <Yz3hLjGCw/bccjFY@localhost>
On Wed, Oct 5, 2022 at 12:55 PM Dominik Vogt <dominik.vogt@gmx.de> wrote:
>
> I wonder if this situation could be prevented by changing the code
> that writes the history file at exit. Is truncating the file to
> zero size part of the procedure? When I need to write a file in a
> safe manner, the procedure normally looks like this:
>
> * Create file.new
> * Rename file to file.old
> * Rename file.new to file
> (* Possibly sync filesystem)
> * Erase file.old
zsh is not going to sync the filesystem for you. Other than that,
though, the default behavior should be close to what you just
described, see the HIST_SAVE_BY_COPY option (which you should make
sure has not been unset).
You might also look at the setting of the HIST_FCNTL_LOCK option.
next prev parent reply other threads:[~2022-10-05 22:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 19:55 Dominik Vogt
2022-10-05 20:01 ` Eric Cook
2022-10-05 20:20 ` Dominik Vogt
2022-10-05 21:05 ` Wesley
2022-10-05 21:24 ` Dominik Vogt
2022-10-05 22:31 ` Bart Schaefer
2022-10-05 23:03 ` Dominik Vogt
2022-10-06 4:34 ` Bart Schaefer
2022-10-06 9:40 ` Peter Stephenson
2022-10-06 10:52 ` Dominik Vogt
2022-10-06 10:30 ` Dominik Vogt
2022-10-05 20:26 ` Dominik Vogt
2022-10-05 22:16 ` Bart Schaefer [this message]
2022-10-05 22:32 ` Dominik Vogt
2022-10-06 10:31 ` Dominik Vogt
2022-10-07 11:45 ` Mikael Magnusson
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=7ZrrKqW35H6uX623KOCe7Bx1BJyCiRzc+F=24spHD6=dA@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=dominik.vogt@gmx.de \
--cc=zsh-users@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).