How to get command line apps to respect the OS X network location. A neat little hack exploiting symlinks and $0.
I can’t think of anything I like better than the intersection of writing and shell hacking.
I recently started a repository for my dotfiles, shell environment, vim config, and utility scripts. As of right now, I’m about 25% through all of the stuff in my $HOME — it should all fill in shortly.
Big list of new features in bash 4.0.
“The syntax for many of the commands in bashdb mimics that of gdb, the GNU debugger. You can step into functions, use next to execute the next line without stepping into any functions, generate a backtrace with bt, exit bashdb with quit or Ctrl-D, and examine a variable with print $foo.”
I threw this together a few weeks ago and now I’m not sure how I lived without it now. I know you people have cool bash/git hacks sitting in your ~/.bashrc — hand them over.
Justin French: alias push?='git cherry -v origin' — beautiful.
Most of these are relevant to POSIX sh(1). This one gets me every time: echo <<EOF :)
Uggghhh. I just spent 30 minutes hunting some arcane tcsh bug caused by coreutils dircolors. This is my revenge. I don’t even know I had any csh code running on this machine. It turns out that MacOS X’s /usr/bin/which is implemented in csh. Dumb.
Dennis Ritchie: “There was a facility that would execute a bunch of commands stored in a file; it was called runcom for ‘run commands’, and the file began to be called ‘a runcom’. rc in Unix is a fossil from that usage.”
Payware GUI shell thingy for MacOS. This is not a QuickSilver/Launchbar clone. It’s more like a magical bash interpreter that knows things about what’s happening in various Mac GUI applications (like Finder, Safari, etc).
“I am going to introduce you to bash’s vi editing mode and give out a detailed cheat sheet with the default keyboard mappings for this mode.”
“Installation is left as an exercise for the reader.”
Looks like they’re bringing the basic capabilities of readline up to the GUI level. Definitely interesting.
“To average users, the suggestion that they use the command line – or the shell, or the terminal, or whatever else you want to call it is only slightly less welcome than the suggestion that they go out and deliberately contract AIDS.” That’s a damn sham
Very nice look at different methods (good and bad) for handling the command line in sh scripts.
Nice look at techniques for writing portable sh.
exec 3<> /dev/tcp/$HOST/80 What?! How cool is that.
A complete look at the little used utilities for processing arguments in scripts.
Anyone who doesn’t know every single one of these probably hasn’t been developing for the web very long. Probably a useful crash course for newbies making their way over from FrontPage or ASP.net though.
Best UNIX productivity article I’ve read in a long while.
… and not just the usual suspects either.
Need to move away from history | grep -i