Live data from Hacker News

How FZF and ripgrep improved my workflow

medium.com

51–60 of 89 posts

Re: How FZF and ripgrep improved my workflow

#51

Using FZF to search the shell history is great until you don't find the command you were searching, you need to abort and what you typed is canceled. That's my only gripe with it. I've tried to play with Zsh's Zle but wasn't able to find a way to abort FZF and retain the input, I suppose I need to modify FZF itself. If there's a way to do it with Zsh I'm all ears...

can you explain what you are looking for i na little more detail?

Re: How FZF and ripgrep improved my workflow

#53

How does ripgrep compare to silversearcher-ag for performance?

I did an extensive comparison a while ago: https://blog.burntsushi.net/ripgrep/ --- It should still largely be pretty accurate (and ripgrep has only gotten faster).

More generally, if someone can find a non-trivial example of ag being faster then ripgrep, then I'd love to have a bug report. (Where non-trivial probably means something like "not I/O bound" and "not so short that the differences are human imperceptible noise.")

Re: How FZF and ripgrep improved my workflow

#54

Earlier quoted context omitted.

Who develops on production servers?

Not everyone is a developer. Still have application and system admins, especially where segregation of duties exists due to security requirements

Non-developers need to change the state of machines on occasion, yes. You're saying there's something about using dotfiles and vim plugins which are inherently less safe than using other open source and proprietary software? Why? (If it's the plug-ins you're worried about there's nothing to stop you forking a version you're happy with; copying to your own corporate repo etc).

Re: How FZF and ripgrep improved my workflow

#55
post #18

Fuzzy down selection (fzf) is the big win. In Emacs that would be Helm of swiper. Instead of local completion (tab tab tab ;) do a global search, and narrow down interactively using fuzzy selection. It's really a different experience, a bit disconcerting at first (tab built into muscle memory), but it quickly becomes a one way change. No way I'd let go of fuzzy selection now. The connection with ripgrep is that fuzzy…

> but it quickly becomes a one way change.

I've been using Helm for a couple of years, and it has crippled all other editors and IDEs for me.

I never read the manual, I have no idea how Helm works, or what it does, or what it is supposed to do. Yet I do use it all day every day. I just type, and Helm delivers what I meant, blazingly fast.

I've tried Atom, VSCode, Eclipse, CLion, Visual Studio, Xcode... I can't use them. You have to click on tabs to switch, you have to click dialogs to open views of the file system, and then navigate them to where you want to go, manually search for the file you want, actually use search boxes somewhere... they all feel super ancient UI wise. Sure, Atom, VSCode, Sublime, they all have some magic box where you can do anything, but that box just isn't Helm.

With Helm I know there is a file or a buffer or anything somewhere containing something that I might need and I don't even know what it is, and I just start pressing keys and Helm goes from showing me the whole universe, to pin pointing me the grain of sand that I didn't know I wanted, by interacting with me.

I have no idea how to even start Helm, nor which keys I press there. Do I press Tab? Sure. What do I press to start interacting with helm ? I don't even know, it just happens. Best tool ever.

Re: How FZF and ripgrep improved my workflow

#57

Using FZF to search the shell history is great until you don't find the command you were searching, you need to abort and what you typed is canceled. That's my only gripe with it. I've tried to play with Zsh's Zle but wasn't able to find a way to abort FZF and retain the input, I suppose I need to modify FZF itself. If there's a way to do it with Zsh I'm all ears...

In Helm you can go back and forth as much as you want. Sometimes you end up in a dark alley, and you are just key press away from stepping back out and trying somewhere else.

Re: How FZF and ripgrep improved my workflow

#58

Earlier quoted context omitted.

That's why emacs users tend to use emacs for everything. Ultimately, everything we do is all text. Editing source code, writing notes, searching through documents, writing emails. It's natural to want to use your favourite tool for all of your text editing needs.

Why would choose such a terrible text editor then?

Honestly? I derive pleasure from hard work. I'm somewhat of a masochist in that way, I guess. I shun convenience and choose the hard path towards personal enlightenment.

Re: How FZF and ripgrep improved my workflow

#59
post #18

Fuzzy down selection (fzf) is the big win. In Emacs that would be Helm of swiper. Instead of local completion (tab tab tab ;) do a global search, and narrow down interactively using fuzzy selection. It's really a different experience, a bit disconcerting at first (tab built into muscle memory), but it quickly becomes a one way change. No way I'd let go of fuzzy selection now. The connection with ripgrep is that fuzzy…

ido-mode was the standard back in the day. I have since moved to ivy/swiper but it was ido-mode that showed me the way some ten years ago (or more). One sad thing about FZF is that it doesn't also support tab-completion. Both ido and ivy support both tab-completion and fuzzy searching at the same time. They compliment each other really well and make these both much more general purpose tools. One import application i…

What made you switch? I'm still using Ido-mode and is quite happy.

Re: How FZF and ripgrep improved my workflow

#60

Earlier quoted context omitted.

I do hope you don't do this on production servers!

Who develops on production servers?

> not having to install and setup additional tools is good, especially when you are using lots of different machines

the person you initially responded to was likely referring to ssh connections to servers

Post reply on HN