sd
fzf
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sd
-
Essential Command Line Tools for Developers
View on GitHub
-
Ripgrep 14 Released
I wanted to like sd but it doesn't support my main use case of recursive search/replace. Imagine every time you wanted to grep some files you had to build a find+xargs+rg pipeline... it just takes me out of the flow too much. I'm glad people are posting other options here, I'm looking forward to trying them.
https://github.com/chmln/sd/issues/62
-
🐚🦀Comandos shell reescritos em Rust
sd
-
sed cheatsheet
https://github.com/chmln/sd ftw (sed rebuilt in rust, much easier imho) ;-)
-
What modern utilities should be a standard part of a modern unixy distro?
sd is a more intuitive alternative to sed, focussing on making find and replace easier - which is all I ever used sed for.
https://github.com/chmln/sd
-
Delete all occurrences of a string
If it's in multiple files? To be honest, I'd just use a terminal and sed (or sd if you want something with a more friendly interface).
- Neovim locks up on big files while doing a replacement
-
sd: your script directory
I love the idea and I'll try it out, but a heads up in case the author is around: the name sd clashes with another tool [0], which works as an alternative to sed.
I use that one pretty often, so maybe my first managed script will be one which symlinks binaries :)
[0] https://github.com/chmln/sd
- Intuitive find and replace CLI (sed alternative)
-
Rust Easy! Modern Cross-platform Command Line Tools to Supercharge Your Terminal
sd is a find-and-replace CLI, and you can use it as a replacement for sed and awk. It is way more user-friendly and modern. It is also magnitudes faster than sed.
fzf
-
Ask HN: Any tool for managing large and variable command lines?
In addition, I think bash's `operate-and-get-next` can be very helpful. When you go back through your shell history, you can hit Ctrl+o instead of enter and it will execute the command then put the next one in your history on the command line, and keep track of where you are in your history. This way, you can rerun a bunch of commands by going to the first one and Ctrl+o till you are done. And you can edit those commands and hit Ctrl+o and still go to the next previously run command.
Note: fzf's history search feature breaks this. https://github.com/junegunn/fzf/issues/2399
-
pyfzf : Python Fuzzy Finder
fzf : https://github.com/junegunn/fzf
- Command Line Fuzzy Search
-
So You Think You Know Git – Git Tips and Tricks by Scott Chacon
Those are the most used aliases in my gitconfig.
"git fza" shows a list of modified/new files in an fzf window, and you can select each file with tab plus arrow keys. When you hit enter, those files are fed into "git add". Needs fzf: https://github.com/junegunn/fzf
"git gone" removes local branches that don't exist on the remote.
"git root" prints out the root of the repo. You can alias it to "cd $(git root)", and zip back to the repo root from a deep directory structure. This one is less useful now for me since I started using zoxide to jump around. https://github.com/ajeetdsouza/zoxide
-
Which command did you run 1731 days ago?
> my history is so noisy I had to find another way
The fzf search syntax can help, if you become familiar with it. It is also supported in atuin [2].
[1]: https://github.com/junegunn/fzf#search-syntax
[2]: https://docs.atuin.sh/configuration/config/#fuzzy-search-syn...
-
Z – Jump Around
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
-
alacritty-themes not working any more!!!
View on GitHub
-
Fish shell 3.7.0: last release branch before the full Rust rewrite
I do find the history pager stuff interesting, but ultimately not of tremendous use for me. I rebound all my history search stuff to use fzf[1] (via a fish plugin for such[2]), and so haven't been aware of the issues
[1] https://github.com/junegunn/fzf
[2] https://github.com/PatrickF1/fzf.fish
-
Ugrep – a more powerful, ultra fast, user-friendly, compatible grep
You can also use fzf with ripgrep to great effect:
[1]: https://github.com/junegunn/fzf/blob/master/ADVANCED.md#usin...
- Tell HN: My Favorite Tools
What are some alternatives?
ripgrep - ripgrep recursively searches directories for a regex pattern while respecting your gitignore
peco - Simplistic interactive filtering tool
neomutt - ✉️ Teaching an Old Dog New Tricks -- IRC: #neomutt on irc.libera.chat
zsh-autocomplete - 🤖 Real-time type-ahead completion for Zsh. Asynchronous find-as-you-type autocompletion.
useful-sed - Useful sed scripts & patterns.
z - z - jump around
hck - A sharp cut(1) clone.
zsh-autosuggestions - Fish-like autosuggestions for zsh
pomsky - A new, portable, regular expression language
mcfly - Fly through your shell history. Great Scott!
joshuto - ranger-like terminal file manager written in Rust
ranger - A VIM-inspired filemanager for the console