From: Dominik Vogt <dominik.vogt@gmx.de>
To: zsh-users@zsh.org
Subject: Re: Bug: Losing .zsh_history
Date: Wed, 5 Oct 2022 22:24:01 +0100 [thread overview]
Message-ID: <Yz318YDhCbJSx4zn@localhost> (raw)
In-Reply-To: <50fa26c9-98aa-1fc7-6bc5-f552a1f450f3@protonmail.com>
On Wed, Oct 05, 2022 at 09:05:44PM +0000, Wesley wrote:
> On 10/5/22 16:20, Dominik Vogt wrote:
> > On Wed, Oct 05, 2022 at 04:01:01PM -0400, Eric Cook wrote:
> >> On 10/5/22 15:55, Dominik Vogt wrote:
> >>> Due to some hardware problem with the display adapter my box
> >>> sometimes fails to show anything on the screen but just emits some
> >>> error beeps while it boots. Since I cannot log in and stop the
> >>> machine without the screen, I can only switch off the power.
> >>>
> >
> > So, I can say with certainty that when this happened I used vim to
> > look at the history file in a 80x24 terminal window and that
> > showed all "^@"s (i.e. 23 lines * 40 nulls = 920 nulls). I'm not
> > sure whether I looked at any other portion of the file, but
> > normally I'd check the last line too. I definitely didn't check
> > what was in between and definitely didn't see anything but nulls.
> > (The last line may be identical to the first line.)
>
> This might be interesting to read:
> https://unix.stackexchange.com/a/273869
Interesting. Actually, my .zsh_history is always "full", so every
time a shell updates the history some of the oldest entries are
removed, i.e. there's normally not a simple append operation.
Appending won't destroy the first line of the file.
> What are your history options btw?
Starting with the default, these are the changes:
setopt APPEND_HISTORY
unsetopt BANG_HIST
setopt HIST_IGNORE_DUPS
setopt HIST_FIND_NO_DUPS
setopt HIST_IGNORE_SPACE
setopt HIST_VERIFY
setopt HIST_EXPIRE_DUPS_FIRST
HISTSIZE=100500
HISTFILE=~/.zsh_history
SAVEHIST=100000
setopt HIST_REDUCE_BLANKS
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
next prev parent reply other threads:[~2022-10-05 21:26 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 [this message]
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
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=Yz318YDhCbJSx4zn@localhost \
--to=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).