What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again.

Delete that bloated snippets file you've been using and share your personal repository with the world. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

Universal configuration monitoring and system of record for IT.

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for:



May 19, 2015 - A Look At The New Commandlinefu
I've put together a short writeup on what kind of newness you can expect from the next iteration of clfu. Check it out here.
March 2, 2015 - New Management
I'm Jon, I'll be maintaining and improving clfu. Thanks to David for building such a great resource!

Top Tags



Psst. Open beta.

Wow, didn't really expect you to read this far down. The latest iteration of the site is in open beta. It's a gentle open beta-- not in prime-time just yet. It's being hosted over at UpGuard (link) and you are more than welcome to give it a shot. Couple things:

  • » The open beta is running a copy of the database that will not carry over to the final version. Don't post anything you don't mind losing.
  • » If you wish to use your user account, you will probably need to reset your password.
Your feedback is appreciated via the form on the beta page. Thanks! -Jon & CLFU Team

Go up multiple levels of directories quickly and easily.

Terminal - Go up multiple levels of directories quickly and easily.
cd() { if [[ "$1" =~ ^\.\.+$ ]];then local a dir;a=${#1};while [ $a -ne 1 ];do dir=${dir}"../";((a--));done;builtin cd $dir;else builtin cd "$@";fi ;}
2009-10-29 21:43:51
User: eightmillion
Functions: cd
Go up multiple levels of directories quickly and easily.

This is a kind of wrapper around the shell builtin cd that allows a person to quickly go up several directories.

Instead of typing:

cd ../..

A user can type:

cd ...

Instead of:

cd ../../..


cd ....

Add another period and it goes up four levels. Adding more periods will take you up more levels.


There are 15 alternatives - vote for the best!

Terminal - Alternatives
alias ..="cd .."; alias ...="cd ../.."; alias ....="cd ../../.."
2009-10-30 01:04:33
User: Tzunamii
Functions: alias
Tags: cd

Change to your taste. Much quicker than having to add 'cd' every time. Add it to your .bashrc or .bash_profile.

alias ..="cd .." ...="cd ../.." ....="cd ../../.."

Know a better way?

If you can do better, submit your command here.

What others think

By using sed, I can reduce your function by 52 characters and extend it to any number of dots!

function cd() { if [[ "$1" =~ "^\.\.+$" ]];then builtin cd "$(echo $1 | sed -e 's/\.//' -e 's/\./..\//g')";else builtin cd "$@";fi }
Comment by flatcap 365 weeks ago

flatcap, I had in mind something like that although your version doesn't seem to work for me on Bash 4.0.33.

I also have some reservations about using external programs for a shell builtin, so I came up with this test function that converts dots into the requisite number of "../"s.

test() { local a dir;a=${#1};while [ $a -ne 1 ];do dir=${dir}"../";((a--));done; echo $dir;}

It would be easy enough to incorporate if I could get that test condition to match correctly.

Comment by eightmillion 365 weeks ago

I managed to get that test to work. I had to unquote the regular expression. Here's the new command that doesn't use any external programs:

cd() { if [[ "$1" =~ ^\.\.+$ ]];then local a dir;a=${#1};while [ $a -ne 1 ];do dir=${dir}"../";((a--));done;builtin cd $dir;else builtin cd "$@";fi ;}
Comment by eightmillion 365 weeks ago


Comment by flatcap 364 weeks and 6 days ago

Your point of view

You must be signed in to comment.