3 ms·
Seconded. Fzf didn't stick with me, but Ripgrep I use a dozen times an hour. It's incredibly fast, and mostly does exactly what I want.
by john-tells-all 5y ago
Seconded. Fzf didn't stick with me, but Ripgrep I use a dozen times an hour. It's incredibly fast, and mostly does exactly what I want.
- kzrdude 5y agoI use fzf to open files in vim. And I use ripgrep's file listing to feed into fzf, so I use both daily together :)
- mustache_kimono 5y agoI think you have to really love the idea of creating an app/script or hot key for a work flow to really start to enjoy using 'fzf'. And for most, I get it, it's "Where to start? Ugh, looks like work." For those that haven't tried yet, and want an entry point, I'd highly recommend you play around with the 'fzf' key bindings and completion scripts for zsh[0] to see what's possible. A little app of mine[1] also has an example of what one might call the minimal viable hot key script for you (note: for skim or 'sk', a 'fzf' Rust clone). [0]: https://github.com/junegunn/fzf/tree/master/shell https://github.com/junegunn/fzf/tree/master/shell [1]: https://github.com/kimono-koans/httm https://github.com/kimono-koans/httm
- b3morales 5y agoFor me the key to using fzf has been remembering that you can pipe ANYTHING into it. For example, grovelling though a git repo with grep might take multiple tries and careful refinement of search patterns. Or you can git log --oneline | fzf and interactively fuzz your way to the commit you're looking for. Having the ability to just update live with backspace when the search isn't matching makes a tremendous difference.
- mustache_kimono 5y agoYep. Awesome.