4 ms·
It's fd, ncdu and sd (sed alternative) for me. https://github.com/chmln/sd https://github.com/chmln/sd https://dev.yorhel.nl/ncdu https://dev.yorhel.nl/ncdu
by girishso 4y ago
It's fd, ncdu and sd (sed alternative) for me.
https://github.com/chmln/sd https://github.com/chmln/sd
https://dev.yorhel.nl/ncdu https://dev.yorhel.nl/ncdu
- plandis 4y agoA while ago I came across this post: https://towardsdatascience.com/awesome-rust-powered-command-line-utilities-b5359c38692 https://towardsdatascience.com/awesome-rust-powered-command-... I’ve also been using bat and exa which are pretty good replacements for cat and ls, respectively. https://github.com/sharkdp/bat https://github.com/sharkdp/bat https://github.com/ogham/exa https://github.com/ogham/exa
- res0nat0r 4y agoscc is an insanely fast alternative to cloc: https://github.com/boyter/scc https://github.com/boyter/scc nnn is also my go to file tree navigation / file moving tool these days too: https://github.com/jarun/nnn https://github.com/jarun/nnn
- pdimitar 4y agoFor counting coding lines I use tokei and I like it: https://github.com/XAMPPRocky/tokei https://github.com/XAMPPRocky/tokei
- 0x00101010 4y agohttps://github.com/kamiyaa/joshuto https://github.com/kamiyaa/joshuto in favor of nnn.
- kbd 4y agoNo file previews yet? I'd stick with ranger or lf.
- mekster 4y agoIt makes you feel less painful reading man pages with bat being the colorized pager. https://github.com/sharkdp/bat#man https://github.com/sharkdp/bat#man
- Self-Perfection 4y agoThis snipper in my ~/.profile colorizes man pages for like ten years already: # Colorify man (changes default $MANPAGER (less) settings) export LESS_TERMCAP_mb='^[[01;31m' export LESS_TERMCAP_md='^[[01;31m' export LESS_TERMCAP_me='^[[0m' export LESS_TERMCAP_se='^[[0m' export LESS_TERMCAP_so='^[[01;44;33m' export LESS_TERMCAP_ue='^[[0m' export LESS_TERMCAP_us='^[[01;32m'
- WalterGR 4y agoncdu is amazing. I foolishly spent way too much time trying to massage du's output into something human-friendly.
- pantsforbirds 4y agosd is my favorite of the newish command line tools. Its super fast and i like the syntax a lot
- kbd 4y agoAgree, I've started replacing my `perl -pe s/.../.../g`s with `sd`. It seems it's actually slightly faster than the equivalent Perl for the same substitutions (which it should be since it does less).
- 1vuio0pswjnm7 4y agohttps://github.com/chmin/sd https://github.com/chmin/sd: "sd uses regex syntax that you already know from JavaScript and Python. Forget about dealing with quirks of sed or awk - get productive immediately." It would be interesting to test the ~1.5GB of JSON the author uses for the benchmark against sed, but there are no details on how many files nor what those files contain. When trying something relatively small and simple, sd appears to be slower than sed. It also appears to require more memory. Maybe others will have different results. sh # using dash not bash echo j > 1 time sed s/j/k/ 1 time -p sed s/j/k/ 1 time sd j k 1 time -p sd j k 1 Opposite problem as the sd author for me. For system tasks, more familiar with faster sed and awk than with slower Python and Javascript, so I wish that Python and Javascript regex looked more like sed and awk, i.e., BRE and occasionally ERE. Someone in the NetBSD core group once wrote a find(1) alternative that had C-like syntax, similar to how awk uses a C-like syntax. Makes sense because C is the systems language for UNIX. Among other things, most of the system utilities are written in it. If the user knows C then she can read the system source and modify/repair the system where necessary, so it is beneficial to become familiar with it. Is anyone is writing system utility alternatives in Rust that use a Rust-like syntax.