My code editor does a fair job of finding things for me, I know I won't use ripgrep/fzf that often :shrug: On the other hand I would recommend fish shell (replacement for bash) with z plugin and http (replacement for curl).
An Illustrated Guide to Useful Command Line Tools
101–108 of 108 posts
Re: An Illustrated Guide to Useful Command Line Tools
#102Lots of cool stuff in here. I’m going to have a long look at Restic and Syncthing. I’d like to know why Skim instead of FZF. They are pretty similar but I’ve been using the latter for years and would like to know of any possible advantages to it.
i loooove syncthing. something i set up recently is a folder called .home_sync to sync my dotfiles between computers. I have a bash script that sets up the symlinks and then version control turned on for the syncthing folder so i can have a record of any changes if I need to revert something
I have a similar setup with Syncthing and a ~/.dotfiles directory, but I recommend GNU Stow to manage symlinking. Simple, ubiquitous and very useful.
Re: An Illustrated Guide to Useful Command Line Tools
#103I’m gonna sound like an old person here. As much as these tools are gorgeous and ergonomic, remember that the others are standard, which means they’re available (almost) everywhere. Still though, these alternatives seem great for productivity locally, even if they’re not usable in a script.
> I’m gonna sound like an old person here. As much as these tools are gorgeous and ergonomic, remember that the others are standard, which means they’re available (almost) everywhere. Well, I, for one, don't work "almost anywhere", I work with specific servers. I ain't gonna get a new server out of the blue. And if some teams works with the same N servers, they can mandate that the tools are present on all of them. P…
You’re right, and I’m not at all against having custom tools in any controlled environment. In fact, I think enhancing a controlled environment with custom tools is extremely productive.
My point was more about education. I think becoming an expert in the standard tools should come before learning any custom ones, because it is a transferable skill.
Re: An Illustrated Guide to Useful Command Line Tools
#104I’m gonna sound like an old person here. As much as these tools are gorgeous and ergonomic, remember that the others are standard, which means they’re available (almost) everywhere. Still though, these alternatives seem great for productivity locally, even if they’re not usable in a script.
ripgrep is included in some linux distros standard now.
In this case, I mean the POSIX standard. But yes, shipping by default in operating systems is how things (eventually) make it into the standard!
Re: An Illustrated Guide to Useful Command Line Tools
#105No mention of things that have gained a lot of traction, like `ag` and `fzf` ag: - silver searcher, fast parallelized recursive grep that can abide by things like `.gitignore` fzf: - fuzzy finder powerline-shell - $PS1 on steroids
I find the to be faster than ag personally
On a simple case, `time rg ^:debug ~/projects`, `ag` appears to be about 10% faster for me, which is negligible for most cases anyway.
Maybe rg is faster on more complex cases?
Re: An Illustrated Guide to Useful Command Line Tools
#106No mention of things that have gained a lot of traction, like `ag` and `fzf` ag: - silver searcher, fast parallelized recursive grep that can abide by things like `.gitignore` fzf: - fuzzy finder powerline-shell - $PS1 on steroids
ripgrep >> ag
and skim is a rust clone of fzf
Re: An Illustrated Guide to Useful Command Line Tools
#107Earlier quoted context omitted.
I find the to be faster than ag personally
On a simple case, `time rg ^:debug ~/projects`, `ag` appears to be about 10% faster for me, which is negligible for most cases anyway. Maybe rg is faster on more complex cases?
Can you reproduce it in a public corpus and file a bug report? ripgrep should never be slower than ag.
Re: An Illustrated Guide to Useful Command Line Tools
#108What about yq, for parsing the increasing amount of yaml? Though there seems to be multiple competing tools by the same name...