Less Commonly Used Unix Commands
81–90 of 95 posts
Re: Less Commonly Used Unix Commands
#82Earlier quoted context omitted.
I still don't get how emacs ever got that image.. I never have to press more than two keys at a time, which is also true for vim..
Then you are doing it wrong. ;) But seriously: How do you do common things such as `query-replace{-regex}` or `indent-region`? Have you rebound them all?
ido-mode is essential. :)
Re: Less Commonly Used Unix Commands
#83A very useful curl switch that I discovered, resume of partially downloaded file ! -C or --continue-at . When offset is "-", curl will use the output file to figure out the offset. curl -C - -o "some_file" It will basically get the size of "some_file" and use it as an offset when making the HTTP request, similar to wget --continue. Very useful to download a file from a unreliable network and when you need all those s…
When I'm on a bad connection, I like to download the file on a server somewhere, then rsync it locally. As long as my server and the server I'm downloading from are on fast connections, the initial step doesn't take long, and this frees me from worrying about expiring cookies or URLs or whatever.
In this case, "Copy cURL" of a request from Chrome's Developer Tools is priceless.
Re: Less Commonly Used Unix Commands
#84Why do programs that only work on OS X always end up on lists of "Unix" programs?
Probably the same reason Linux users would put Linux programs on such a list — it's relevant to them and probably much of their audience.
Re: Less Commonly Used Unix Commands
#85I 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…
Re: Less Commonly Used Unix Commands
#86I was really enjoying the fact you had a tl;dr next to each one. Then I noticed this wget: get w’s Ok, if I didn't know what wget did already that wasn't too useful. But then it gets worse vim: attack yourself man units: interesting ddate: wtf
watch: execute something on a schedule *in realtime*
printf: change the format of output
apropos: info on commands
dd: disk writing
ss: socket statistics (show apps *using the Internet*)
Almost but not quite.Re: Less Commonly Used Unix Commands
#87Plenty 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.
> Plenty on this list are well known... My thoughts exactly. Time, df, du, iostat, watch, htop, wget, tmux, .... Really?
Re: Less Commonly Used Unix Commands
#88Why do programs that only work on OS X always end up on lists of "Unix" programs?
Re: Less Commonly Used Unix Commands
#89Plenty 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.
> Plenty on this list are well known... My thoughts exactly. Time, df, du, iostat, watch, htop, wget, tmux, .... Really?
Re: Less Commonly Used Unix Commands
#90ls -1 /usr/bin/ | sed '/^.\{1,6\}$/!d' |xargs whatis '{}' 2> /dev/null | less