Live data from Hacker News

So you've installed `fzf` – now what?

andrew-quinn.me

121–130 of 292 posts

Re: So you've installed `fzf` – now what?

#121
> I reviewed my options. I could > Use my half-remembered knowledge of the FHS to guess around, with trees and greps, or > Just know and commit it to memory and feel superior to everyone else, or > Just pipe find . ‘/’ to fzf and start searching.

Or you could have just typed find / -name nginx.conf

Maybe an extra 2>/dev/null if you dont want to do it from sudo

Re: So you've installed `fzf` – now what?

#123

I love fuzzy shell history. Game changer in terms of shell productivity. I use atuin[0] instead of fzf as I find the experience a bit nicer and it has history backups built in (disclaimer, I am a maintainer) Some of our users still prefer fzf because they are used to how it fuzzy finds, but we're running an experiment with skim[1] which allows us to embed the fuzzy engine without much overhead - hopefully giving them…

I'm a fan of McFly https://github.com/cantino/mcfly

Re: So you've installed `fzf` – now what?

#124
post #73

Other uses for fzf: - Combine it with autojump[1] and quickly navigate to any directory you've navigated to before (sorted by frequency). This is crazy helpful. - Use it for git branch names - Use it for ssh locations [1] https://github.com/wting/autojump

how do I use it with autojump?

Re: So you've installed `fzf` – now what?

#125

Earlier quoted context omitted.

I also had a rather noticeable delay when launching atuin. As it turns out, this was because it checked for an update every time it launched! You can disable that update check: add a ` update_check = false` to your `~/.config/atuin/config.toml` [1]. That made the delay pretty much disappear for me. [1]: https://atuin.sh/docs/config/#update_check

We actually fixed the delay issue, but since you disabled update checking you wouldn't have known to update! It was quite annoying so we're sorry for that

How would you compare this to, say, McFly? https://github.com/cantino/mcfly

Re: So you've installed `fzf` – now what?

#126
The article talks about rg (ripgrep) but not rga (ripgrepall)[1] which extends rg to other file types like pdf, tar, zip. The rga website provides a function on integrating it with fzf[2] to interactively search documents from terminal.

[1] https://github.com/phiresky/ripgrep-all

[2] https://github.com/phiresky/ripgrep-all/blob/master/doc/rga-...

Re: So you've installed `fzf` – now what?

#128

> I reviewed my options. I could > Use my half-remembered knowledge of the FHS to guess around, with trees and greps, or > Just know and commit it to memory and feel superior to everyone else, or > Just pipe find . ‘/’ to fzf and start searching. Or you could have just typed find / -name nginx.conf Maybe an extra 2>/dev/null if you dont want to do it from sudo

Notice in that section I called it within a subshell. If I ran `vi $(find / -name nginx.conf)`, and there happened to be multiple files named nginx.conf lying around my system, my guess is `vi` would try to open all of them as different buffers, which is not generally what I want.

Re: So you've installed `fzf` – now what?

#129

Earlier quoted context omitted.

We actually fixed the delay issue, but since you disabled update checking you wouldn't have known to update! It was quite annoying so we're sorry for that

How would you compare this to, say, McFly? https://github.com/cantino/mcfly

Not too different.

* We use heuristic based searches whereas mcfly trains a neural network * We offer a sync functionality to share history on multiple machines

mcfly is a great project, although they are looking for new maintainers apparently!

Re: So you've installed `fzf` – now what?

#130
post #73

Other uses for fzf: - Combine it with autojump[1] and quickly navigate to any directory you've navigated to before (sorted by frequency). This is crazy helpful. - Use it for git branch names - Use it for ssh locations [1] https://github.com/wting/autojump

how do I use it with autojump?

autojump -s gets you the entries in the database.

You have to parse it to extract the directories without all the metadata it spits out.

Then you probably need to write a shell function in your preferred shell to tie the pieces together, as well as assign it to a keybinding. It's not too hard.

I use xonsh for my shell, so my config probably won't help. And doing it in xonsh is probably a lot messier than doing it in Bash.

Post reply on HN