61–70 of 95 posts
Earlier quoted context omitted.
I aliased `cd` to pushd (squelching output) and `dc` to popd in my interactive shell. It's super handy to have a back button for my shell.
dc(1) is also an RPN calculator, which comes in handy sometimes.
popd and pushd are commands that, once learned, I thought would change my life forever. Turns out, not so much. :| EDIT: 'watch mtr' is handy for keeping an eye on your network connection, and finding slowdowns.
Agreed. The game changer for me turned out to be: https://github.com/rupa/z It has an uncanny knack for getting me to where I want to go with very little in the way of input.
I found jq the other day ( http://stedolan.github.io/jq/ ), which is a commandline utility for manipulating json data, resembling awk. Considering the number of API's that return json data these days, it's simplified my life a great deal. It's proven especially useful for automation shell scripts, when working with things like the aws command line client that return all results as json. Usually I'm looking to extract…
Earlier quoted context omitted.
Agreed. The game changer for me turned out to be: https://github.com/rupa/z It has an uncanny knack for getting me to where I want to go with very little in the way of input.
fzf completely replaces z, and is ridiculously fast. https://github.com/junegunn/fzf
Plenty on this list are well known but there are some nice ones that either I'd forgotten about or didn't know : column, ss, comm, fc I'd add the following to the list : printf , bc Also, "ddate" is fun. I had no idea and just spent an enjoyable 10 minutes looking it up. Thanks for posting this.
My thoughts exactly. Time, df, du, iostat, watch, htop, wget, tmux, ....
Really?
That's definitely useful.
I found jq the other day ( http://stedolan.github.io/jq/ ), which is a commandline utility for manipulating json data, resembling awk. Considering the number of API's that return json data these days, it's simplified my life a great deal. It's proven especially useful for automation shell scripts, when working with things like the aws command line client that return all results as json. Usually I'm looking to extract…
+1 for jq. Lifechanging. I had to build it on CentOS6, but as you said, super easy.
It would be very useful to delineate this list by command type and availability. The ones I wanted to check out (ndiff, rs, iftop, mtr, ...) must be in packages, since they don't respond in either OS X or vanilla Debian.
Worth it for sshfs alone.
A friend of mine once commented "If you need to use sshfs, you've already lost"
So really it just depends on what you're trying to do as to the practicality of sshfs. But then I guess you could argue that is the case for nearly all the commands that many sysadmins have flamewars over.