Earlier quoted context omitted.
If you want to do that this is the actual lib https://github.com/saghen/frizbee
Blink is for completion, not fuzzy find.
Fff.nvim – Typo-resistant code search
11–17 of 17 posts
Re: Fff.nvim – Typo-resistant code search
#12At least point to the lib not the software https://crates.io/crates/neo_frizbee This is where the typo resistance comes from.
Why? The author is a contributor to that project. What’s wrong with posting this project?
Re: Fff.nvim – Typo-resistant code search
#13Re: Fff.nvim – Typo-resistant code search
#14We need that for Emacs
Re: Fff.nvim – Typo-resistant code search
#15As someone whose core workflow in neovim involves no tabs, limited panes/split views and a copious amount of 'ff' (while also being incapable of spelling), this tickles me right where I itch.
My current fuzzy find key combinations include:
ff: fuzzy find, limited to current project
fc: fuzzy find (c)ode -> expand search scope to all projects
fg: fuzzy find (g)lobal -> let's just search my entire home folder
I imagine I'd have to limit it to the first and remap 'fg', I use 'gf', 'gc', 'gg' for the grep versions of these commands.
Either way, very cool.
Re: Fff.nvim – Typo-resistant code search
#16i used it and I really like it, the only thing that annoys me is every time i need to rebuild rust bindings
They have prebuilt binaries now for fff
Re: Fff.nvim – Typo-resistant code search
#17I've been using this for a few months now and it's amazing. Crazy fast and the vast majority of the time I get the result I want in one shot.