Fzf – the basics part 1 – layout
qmacro.org
Fzf – the basics part 1 – layout
1–10 of 40 posts
Re: Fzf – the basics part 1 – layout
#2Re: Fzf – the basics part 1 – layout
#3I learned that the built in history search in bash requires one less key press to use.
Re: Fzf – the basics part 1 – layout
#4fzy[1] is a less bloated alternative, written in C. fzf is neat, but it does too much. [1]: https://github.com/jhawthorn/fzy
Also, I fully appreciate not rewriting things that are C and already working just because -- but surely if something is already written in a safer language then C isn't really a step forward either.
Re: Fzf – the basics part 1 – layout
#5fzy[1] is a less bloated alternative, written in C. fzf is neat, but it does too much. [1]: https://github.com/jhawthorn/fzy
Re: Fzf – the basics part 1 – layout
#6fzy[1] is a less bloated alternative, written in C. fzf is neat, but it does too much. [1]: https://github.com/jhawthorn/fzy
But neither fzy nor skim quite do what fzf does, which is offer an simple feature-filled experience out of the box. The big draw is fzf Just Works™. I don't mind that it feels bloated and slow sometimes, because I don't want to spend a week figuring out how to make the other two do what fzf does without configuration or drama, and all the speed improvements in the world doesn't really matter when the bottleneck is the meatball behind the keyboard.
Re: Fzf – the basics part 1 – layout
#7Re: Fzf – the basics part 1 – layout
#8Re: Fzf – the basics part 1 – layout
#9Fzf might be my most used command line utility. That and autojump (alias to j).
Re: Fzf – the basics part 1 – layout
#10Fzf might be my most used command line utility. That and autojump (alias to j).