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

tar the current directory wihtout the absolute path

Terminal - tar the current directory wihtout the absolute path
ORIGDIR=${PWD##*/}; PARENT=`dirname $PWD`; tar -C $PARENT -cf ../${ORIGDIR}.tar $ORIGDIR
2013-11-04 18:44:34
User: vwal
Functions: tar
tar the current directory wihtout the absolute path

tars the current directory (and its children) in an archive of the same name (plus ".tar" :)) in the parent directory without the absolute path, so that when the archive is extracted, only the current directory name is created for the path. Assumes bash/zsh.


There is 1 alternative - vote for the best!

Terminal - Alternatives
tar -cf "../${PWD##*/}.tar" .
2013-11-06 11:15:38
User: joedhon
Functions: tar

should do the same as command #12875, just shorter.

Know a better way?

If you can do better, submit your command here.

What others think

Hmm... An example might help people understand better.

I had to try out the command to be certain what it did :-)

I can think of two shorter ways of getting the same result:

(D=${PWD##*/}; cd ..; tar cf "$D.tar" "$D")

In a subshell (), find our directory name ($D), go up one directory and create a tar file.

The subshell means that tar is run in .. but we stay where we were.

The alternative (if you don't mind a harmless tar warning) is:

D=${PWD##*/}; tar cf "../$D.tar" "../$D"

tar will warn you about, but ignore, the leading ../

Note: I have quoted all the paths just in case the directory name contains whitespace.

Comment by flatcap 181 weeks and 3 days ago

I'm curious what's wrong with giving the path of '..' for parent dir to tar? Something like:

D=${PWD##*/} ; tar -C .. -cf "../$D.tar" "$D"
Comment by pdxdoughnut 181 weeks and 3 days ago

You can shorten this to: tar -cf ../$(basename $PWD).tar .

Comment by joedhon 181 weeks and 2 days ago

pdxdoughnut's version is probably optimal (shorter than my proposed version). joedhon's version, however, doesn't preserve the current folder name without the above path which was the whole point of my original command.

Comment by vwal 181 weeks ago

Your point of view

You must be signed in to comment.