Check These Out
works with fractions like 1/3.5
M - current revision, N - older revision
On the Mac, the format ifconfig puts out is little different from Linux: the IP address is space separated, instead of colon. That makes parsing the IP address easier. See releated command for Linux/Unix:
http://www.commandlinefu.com/commands/view/651/getting-the-ip-address-of-eth0
This is the setup I'm using for my largest project. It gives 357 lines per page (per side), which makes it fairly easy to carry around a significant amount of code on a few sheets of paper. Try it.
(I stick to the 80 column convention in my coding. For wider code, you'll have to adjust this.)
I always add this to my .profile rc so I can do things like: "vim *.c" and the files are opened in tabs.
Very useful when you need disk space. It calculates the disk usage of all files and dirs (descending them) located at the current directory (including hidden ones). Then sort puts them in order.
When using reverse-i-search you have to type some part of the command that you want to retrieve. However, if the command is very complex it might be difficult to recall the parts that will uniquely identify this command. Using the above trick it's possible to label your commands and access them easily by pressing ^R and typing the label (should be short and descriptive).
UPDATE:
One might suggest using aliases. But in that case it would be difficult to change some parts of the command (such as options, file/directory names, etc).
Within /proc and /sys there are a lot of subdirectories, which carry pseudofiles with only one value as content. Instead of cat-ing all single files (which takes quite a time) or do a "cat *" (which makes it hard to find the filename/content relation), just grep recursively for . or use "grep . /blabla/*" (star instead of -r flag).
For better readability you might also want to pipe the output to "column -t -s : ".
If you issue the "set" command, you'll see a list of variables and functions. This command displays just those functions' names.