by zan on 3/13/15, 3:59 PM with 47 comments
by tensorproduct on 3/13/15, 7:05 PM
edit: Actually, something cool I learned recently is that if you put the line "set editing-mode vi" in your ~/.inputrc then vi-like editing keys are available in any program that uses readline. This includes bash and the python repl. Presumably, a bunch of other repls and interactive command lines too.
by guruparan18 on 3/13/15, 5:43 PM
I ended up highly optimizing my work environment to replace long ssh connections with `conn prod` (will use my RSA key and connect). File tranfers with `go get prod filename` or `go send prod filename`. Another script that can remember directory paths (I have to go over lot of them every day, and typing long lengthy ones does not help).
To me, UNIX shell scripting is a lazy men's most effective tool, only if you know how to use that rightly.
Loved the post. And thanks much.
by lukabratos on 3/13/15, 4:01 PM
by bcook on 3/13/15, 6:43 PM
The book "Unix Power Tools" showed me that higher-level programming languages (Perl, Python, Ruby, etc) are not needed to accomplish most administrative tasks. Awk is incredibly useful (but also very confusing, imo).
by babuskov on 3/13/15, 6:40 PM
You can use slash(/) and question mark(?) to search for text (forward and backward) in vi. It's useful to know these, because they also work with less(1).
If you are Windows user and used to press Ctrl+S to save the file and you accidentally do that in Vi, your terminal would get stuck. But you can use Ctrl+Q to unfreeze it.
by nicksuperb on 3/13/15, 8:08 PM
Words to live by.
by olalonde on 3/14/15, 1:53 AM
$ which -a ruby
/Users/olalonde/.rbenv/shims/ruby
/usr/local/bin/ruby
/usr/bin/ruby
by kbaker on 3/13/15, 6:04 PM
by zan on 3/13/15, 10:48 PM
by voidhorse on 3/13/15, 7:57 PM
Actually, I think most people who use computers at work, be they writers, designers, whatever, not just programmers, would benefit from learning some bash (or batch). You can automate a lot of useful processes with a few simple scripts.
by blueblob on 3/13/15, 5:38 PM
by throw7 on 3/13/15, 6:44 PM
2. If you want to save your command without running it... comment it out with a '#'. Bang, it's in your history.
by tieTYT on 3/13/15, 6:44 PM