From: Perette Barella <perette@barella.org>
To: Roman Perepelitsa <roman.perepelitsa@gmail.com>
Cc: zsh-workers@zsh.org
Subject: Re: zsh: corrupt history file
Date: Wed, 29 Jul 2020 11:15:40 -0400 [thread overview]
Message-ID: <271b648e-9c30-3333-cfca-dedf8df9e248@barella.org> (raw)
In-Reply-To: <CAN=4vMro1cy6FvD+2zM7zsY9cwCscYVYAt4soVcshaHS0BY1bQ@mail.gmail.com>
I tracked down the export, removing it works. Must have put that in the
.zshrc 5 years ago, when I first looked at it, before deciding it was
broken because the history kept getting corrupt.
Perhaps update the man page for $HISTFILE:
HISTFILE
The file to save the history in when an interactive shell exits. If
unset, the history is not saved.
Do not export this parameter, as doing so may cause other shells to
corrupt the history file.
Thanks Roman,
Perette
On 2020-07-29 10:39, Roman Perepelitsa wrote:
> On Wed, 29 Jul 2020 at 16:33, Perette Barella <perette@barella.org
> <mailto:perette@barella.org>> wrote:
>
> Research on Google suggests the 'corrupt history file' problem is rare.
> In my experience, it is not
>
>
> Are you perchance exporting HISTFILE? You shouldn’t.
>
> Roman.
>
--
Perette Barella • 176 Middlesex Road, Rochester NY 14610 • 585-317-3013
"Once we realize that imperfect understanding is the human condition
there is no shame in being wrong, only in failing to correct our
mistakes." -- George Soros
next prev parent reply other threads:[~2020-07-29 15:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 14:32 Perette Barella
2020-07-29 14:39 ` Roman Perepelitsa
2020-07-29 15:15 ` Perette Barella [this message]
2020-07-29 15:21 ` Eric Cook
2020-07-29 23:07 ` Daniel Shahaf
2020-07-30 3:56 ` Eric Cook
2020-07-30 4:30 ` Daniel Shahaf
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=271b648e-9c30-3333-cfca-dedf8df9e248@barella.org \
--to=perette@barella.org \
--cc=roman.perepelitsa@gmail.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).