Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Merging history does not work #3496
related: History synchronization
fish version installed (
No trace of
I've looked through your config files and cannot find anything related to this (though I don't know your plugins). I could critique them if you want me to, though.
Can you try without configuration?
It's expected that the command you ran in session fish-1 isn't in the history of session fish-2 until you run
P.S., With the soon to be available 2.4.0 release this becomes
Again, is tmux actually relevant here? Can you reproduce this without tmux, just with multiple terminals or tabs in yakuake/konsole?
And can you confirm that you also do not see
~/.local/share/fish/fish_history (or $XDG_DATA_HOME/fish/fish_history, if that variable is defined).
The problem is because you're defining a unique
No suggestion either
That seems like #2335, which was supposed to be fixed in 2.3.0. When you fix the permissions and do stuff like run fish in
Just to be clear, you could also remove the file, but then you need to ensure that it is created first with the correct permissions, ie. run some commands and ideally
I'm having this exactly same issue with the last git version. I opened two fish instances using a temp dir for home, and when I do a
Basically, it looks like the most recently executed command doesn't merge, but sometimes its even several of the last commands.
I'm looking at
What would cause
What you're seeing, @cjthompson, is a different problem. Based on my testing what is happening is that sometimes a fish instance doesn't notice that fish history file has changed and continues writing to an old, no longer existing, history file. Which also means that when you do
You can see this by running
@cjthompson: Can you confirm what I wrote above explains why history syncing doesn't work for you?
referenced this issue
Nov 19, 2016
I'll bet this is a funny ordering problem due to history commands manipulating the history and also expecting to be in the history.
Edit: could also be
Edit2: d'oh, I think we're just forgetting to update