As can be seen, my target is command as-cmd -b
, fzf finds it and also fzf has more results compared to atuin.
I am using fish, atuin is my default, to check fzf in fish i ran fzf --fish | source
As can be seen, my target is command as-cmd -b
, fzf finds it and also fzf has more results compared to atuin.
I am using fish, atuin is my default, to check fzf in fish i ran fzf --fish | source
Does anything in here looks like it matches your description?
Is Highlight part of query being matched in search history similar to fzf basically the same problem?
I think this [Bug]: Atuin fzf search to behave the same like my zsh fzf search · Issue #2351 · atuinsh/atuin · GitHub
and maybe Fuzzy search unexpectedly favors old entries · Issue #1049 · atuinsh/atuin · GitHub
Also, i just tried using search_mode = “skim”
and it has better results than using ”fuzzy”
. But i want to use ”fuzzy”
as the syntax will be same as fzf
Mh yeah I see! I also just tried out skim as well and can see the problem.
Just started using atuin myself and come from fzf too, so I can really relate to your pains with this
Yes, i wanted to see what is matching what, fzf queries search start from beginning of text. i.e if i search for kmo res tem
it will match sudo systemctl restart kmonad@
, as can be seen kmo
is in fourth word, res
is in third word, and tem
is second word. The order of query is different from the result.
@ellie can you please take a look at this.
Existing issue mentioning this →
Definitely open to exploring this, but the main issue is that existing implementations don’t tend to store and index to disk
Actually one of the very earliest Atuin versions used fzf - there was a very noticeable latency while it built its index on startup
Because of that, we’ve tried to build an approximation with SQL, which is naturally not quite the same