fisher VS fd

You've got to install Fisher, then get z, sponge and a few others from the awsm.fish list.

Then you get trapped by the utility and struggle when you land on some remote server's bash shell.

https://github.com/jorgebucaran/fisher

https://github.com/jorgebucaran/awsm.fish#readme

If you're running a script, you can use edc/bass to run it from a fish shell. Fisher is one of the first things I install after fish, then bass, z and a few other helper plugins.

https://github.com/edc/bass

https://github.com/jorgebucaran/fisher

As a minimalist plugin manager for Fish, I recommend fisher. I've created a plugin that can be installed via fisher and integrated into any Fish environment. If there are any reasons why you don't want to use Fisher, you can just copy-paste conf.d/autoenv.fish file to your ~/.config/fish/conf.d directory.

Fish is a acronyn for friendly interactive shell. It is a smart and user friendly shell for Unix-like operating systems like Linux. There are a lot of features that make it stand out from other shells like bash. It has a lot of features like autosuggestions, syntax highlighting, tab completions and a lot more. You can read more about it in the documentation. I have been using it for a while now and I it configured to my liking. In terms of plugins I use fisher to manage my plugins. I have a couple of plugins that I use on a daily basis. I have listed them below:

stay away from Oh-My-Fish - you probably don’t need it - Fish is pretty awesome out of the box, and if you do want a plugin or two Fisher is a much better route.

Agreed. I personally like Fisher (https://github.com/jorgebucaran/fisher) with this theme based on Powerlevel10k (https://github.com/IlanCosman/tide)

Fisher is a simple and convenient plugin manager for Fish. With a single command, you can install new plugins, update them, or remove them, without ever having to change any file. Convenient! Therefore, I recommend to install it to simplify your plugin management.

You can install it quickly using fisher:

I use https://github.com/jorgebucaran/fisher

ripgrep: A super-fast file searcher. You can install it using your system's package manager (e.g., brew install ripgrep on macOS). fd: Another blazing-fast file finder. Installation instructions can be found here: https://github.com/sharkdp/fd

hyperfine is such a great tool that it's one of the first I reach for when doing any sort of benchmarking.

I encourage anyone who's tried hyperfine and enjoyed it to also look at sharkdp's other utilities, they're all amazing in their own right with fd[1] being the one that perhaps get the most daily use for me and has totally replaced my use of find(1).

[1]: https://github.com/sharkdp/fd

You call it with `n` and get an interactive fuzzy search for your directories. If you do `n ` instead, it’ll start the find with `` already filled in (and if there’s only one match, jump to it directly). The `ls` is optional but I find that I like having the contents visible as soon as I change a directory.

I’m also including iCloud Drive but excluding the Library directory as that is too noisy. I have a separate `nl` function which searches just inside `~/Library` for when I need it, as well as other specialised `n` functions that search inside specific places that I need a lot.

¹ https://github.com/sharkdp/fd

² https://github.com/junegunn/fzf

Many (most?) of them have been overhauled with success. For find there is fd[1]. There's batcat, exa (ls), ripgrep, fzf, atuin (history), delta (diff) and many more.

Most are both backwards compatible and fresh and friendly. Your hardwon muscle memory still of good use. But there's sane flags and defaults too. It's faster, more colorful (if you wish), better integration with another (e.g. exa/eza or aware of git modifications). And, in my case, often features I never knew I needed (atuin sync!, ripgrep using gitignore).

1 https://github.com/sharkdp/fd

Descubra mais sobre o fd em: https://github.com/sharkdp/fd

AFAIK there is a find replacement with sane defaults: https://github.com/sharkdp/fd , a lot of people I know love it.

However, I already have this in my muscle memory:

fd

> without zsh globs I have to remember find syntax

My "solution" to this is using https://github.com/sharkdp/fd (even when in zsh and having glob support). I'm not sure if using a tool that's not present by default would be suitable for your use cases, but if you're considering alternate shells, I suspect you might be

Nice to see other alternatives to find. I personally use fd (https://github.com/sharkdp/fd) a lot, as I find the UX much better. There is one thing that I think could be better, around the difference between "wanting to list all files that follow a certain pattern" and "wanting to find one or a few specific files". Technically, those are the same, but an issue I'll often run into is wanting to search something in dotfiles (for example the Go tools), use the unrestricted mode, and it'll find the few files I'm looking for, alongside hundreds of files coming from some cache/backup directory somewhere. This happens even more with rg, as it'll look through the files contents.

I'm not sure if this is me not using the tool how I should, me not using Linux how I should, me using the wrong tool for this job, something missing from the tool or something else entirely. I wonder if other people have this similar "double usage issue", and I'm interested in ways to avoid it.