Earlier quoted context omitted.
apt install? There's no way I'm integrating a core tool like that with a crude "curl | zsh" hack. How and when would it get updated? Am I expected to stick that in an Ansible playbook?
Yes. It's a shell hook, it's expected for you to add it to your bash/zsh .rc yourself. How else can it work?
So you've installed `fzf` – now what?
111–120 of 292 posts
Re: So you've installed `fzf` – now what?
#112Re: So you've installed `fzf` – now what?
#113Earlier quoted context omitted.
> For Alt+C, are peoples’ file and directory layouts such a mess that they need to search entire directory trees to find what they’re looking for? Have you ever joined a new project? Usually they're both messy and you don't know where anything is. Besides, even now with plenty of familiarity in my current legacy code base I can use fzf to type filenames or directories without typing the full path. Ctrl+R is great for…
>Have you ever joined a new project? Shouldn't your new team members work to help onboard you instead? Shouldn't you get ample training in your job?
Re: So you've installed `fzf` – now what?
#114Earlier quoted context omitted.
I wanted to like atuin. The idea is great. But it just could not match the instant search that ctrl-r with fzf offers sadly. There is always a noticeable delay that annoyed me and made me revert back to fzf for search. For me another issue was that I needed to do more keystrokes for the same behaviour (search a previously ran command and execute it). Fuzzy shell history search is just one of those mind-blowing things…
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 introduced this as we found a lot of people reporting bugs that had already been fixed + they just needed to update, or users on the sync server that were >1yr behind on updates (making improvements really difficult to introduce).
Re: So you've installed `fzf` – now what?
#115have no need for this, plenty fast without it. these two have been sufficient for all my needs: ctrl + r for most things history | grep for searching when i forget the exact command or want to see related commands. I don't want pull downs, pull ups, drop downs, expanded hamburger menu, hot dogs, another set of key strokes to remember how i started some service last month.
You seem to be stuck in your ways, so that even when new better alternatives are created, you dismiss them unceremoniously, possibly without having taken the time to evaluate them.
It's something I've noticed with quite a few linux users, and I find that super interesting!
May I ask what's your age range? (just curious)
Do you think the time spend in an exploratory phase for new tools (ex: getting familiar with fzy) would not be recovered by time gains in the exploitation phase? Or is it because of a fear of the unknown, or a belief that old habits may be hard to change?
It's a very serious question BTW, I hope it's not too personal
Re: So you've installed `fzf` – now what?
#116Is there a preceding blog post I could read here? Something like, "So you've just heard of fzf for the first time, what even is it?" I was kind of surprised that the author doesn't even make a passing attempt to define or explain it.
https://www.redhat.com/sysadmin/fzf-linux-fuzzy-finder
The tl;dr is that it provides terminal fuzzy finding that can be plugged into just about any task that involves finding things.
I use it many times an hour, it's the main way I navigate files and buffers in nvim, it's how I find files in my projects, it's how I select sessions in tmux.
I'd be lost without it.
Re: So you've installed `fzf` – now what?
#117Earlier quoted context omitted.
apt install? There's no way I'm integrating a core tool like that with a crude "curl | zsh" hack. How and when would it get updated? Am I expected to stick that in an Ansible playbook?
Yes. It's a shell hook, it's expected for you to add it to your bash/zsh .rc yourself. How else can it work?
Re: So you've installed `fzf` – now what?
#118I don't think this article goes far enough into what a game-changer fzf can be. Combined with some clever "preview" functions, and a pop-up terminal function (which, that part is admittedly harder than it ought to be) it can be an across the board a better general purpose script menu creator than most command line AND GUI tools, namely due to - instant previews AND - the ability to either arrow up and down OR fuzzy t…
Re: So you've installed `fzf` – now what?
#119I 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…
Re: So you've installed `fzf` – now what?
#120I 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…