Live data from Hacker News

Fzf – the basics part 1 – layout

qmacro.org

1–10 of 40 posts

Re: Fzf – the basics part 1 – layout

#4
post #2

fzy[1] is a less bloated alternative, written in C. fzf is neat, but it does too much. [1]: https://github.com/jhawthorn/fzy

But does it really? Can one not simply not use the features one doesn't need?

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

#6
post #2

fzy[1] is a less bloated alternative, written in C. fzf is neat, but it does too much. [1]: https://github.com/jhawthorn/fzy

There's also skim[1], which would be a Rust fzy alternative.

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.

[1]https://github.com/lotabout/skim

Re: Fzf – the basics part 1 – layout

#8
This thing is magical! I use it as a quick scientific paper finder. Basically have a folder with, probably thousands by now, papers (each file's name contains paper title, authors, year, journal) and by typing a couple words can fuzzy search for stuff by whatever fields. It also works incredibly nicely with vim as a fuzzy search for either files or phrases within files.
Post reply on HN