You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been increasingly encountering this problem for the past few months. It manifests after I first log in. When I type history, no history is printed, even though the fish_history file still exists and contains earlier history.
The last time it happened, I noticed there were embedded NUL bytes in fish_history with a newer entry. (screenshot included)
When I removed the entry containing the NUL bytes, and logged out & in, things worked normally.
(Before staring X)
$ echo $TERM
linux
(Within X)
$ echo $TERM
tmux-256color
$ fish --version
fish, version 3.7.1
$ uname -srm
Linux 6.8.9-arch1-1 x86_64
$ fisher list
jorgebucaran/fisher
jethrokuan/z
$ tmux -V
tmux 3.4
/ is ext4
$ wc --lines fish_history.BAD
141748 fish_history.BAD
The text was updated successfully, but these errors were encountered:
(Adaptedfrom this comment #10300 (comment))
I've been increasingly encountering this problem for the past few months. It manifests after I first log in. When I type
history
, no history is printed, even though thefish_history
file still exists and contains earlier history.The last time it happened, I noticed there were embedded NUL bytes in fish_history with a newer entry. (screenshot included)
When I removed the entry containing the NUL bytes, and logged out & in, things worked normally.
(Before staring X)
$ echo $TERM
(Within X)
$ echo $TERM
$ fish --version
$ uname -srm
$ fisher list
$ tmux -V
/
is ext4$ wc --lines fish_history.BAD
The text was updated successfully, but these errors were encountered: