1
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?
KAGEYAM4 4
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 
KAGEYAM4 6
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 8
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
ellie 9
just an update for you all!
with the release of 18.13.2, we now ship a new search mode. This is much more like the search you’d get with fzf, as it uses nucleo behind the scenes. It requires that you use the Atuin Daemon - it keeps a search index warm and in-memory, so that it doesn’t require building from scratch every time
To enable, you have two options
- Run
atuin setup, say yes to the daemon. Good to go. - Edit your
config.toml, with the following changes
search_mode = "daemon-fuzzy"
[daemon]
enabled = true
autostart = true
ellie 10
I’ve marked the above as the solution so it shows more clearly for those coming via search engines. Please lmk if it still does not behave as expected
ellie 11
We’re shipping v18.19 on Monday, with an even better daemon fuzzy search. It’s much faster than before