7 ms·
How little you know, and some useful commands.
- Estragon 16y agoCtrl-X E didn't work for me. Anyone know what shell that's for? (I'm using bash.)
- tenaciousJk 16y agoWatching Star Wars via telnet... I've been looking for that command for ages.
- nlo 16y agoWithin the past year I discovered dig's +short parameter, which let me retire some scripts I had for parsing just the IPs out of dig's output. e.g.: dig +short google.com
- shii 16y agoYeah +short is pretty cash. I alias this[1] little magic glue to wiki and use that a lot instead of wasting precious milisecs on HTML and silly styling. [1]: http://www.commandlinefu.com/commands/view/2829/query-wikipedia-via-console-over-dns http://www.commandlinefu.com/commands/view/2829/query-wikipe...
- dsakima 16y agoCtrl+r instead of history | grep
- ajays 16y agoThe "@" command is pretty useful too, for doing arithmetic on shell variables. % set i = 1 % echo $i 1 % @ i++ % echo $i 2 % @ i *= 2 % echo $i 4
- thangalin 16y agoBad example: $ ls -l 500.* $ ^500^600 Fewer keystrokes (using bash): $ ls -l 500.* Up-arrow, control-left, delete, 6
- shubber 16y agoMy favorite bash trick is still Ctrl-O: submit command and advance history by one. If you ever find yourself counting up-arrows to repeat a sequence of commands (that aren't worth scripting for whatever reason), next time, go to the top of the list and hit Ctrl-O. The result is the the command runs, and the one after it in the history is loaded into you prompt.