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.

If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

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:



2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.

Top Tags



Isolate file name from full path/find output

Terminal - Isolate file name from full path/find output
echo ${fullpath##*/}
2010-07-21 22:35:29
User: quincymd
Functions: echo
Isolate file name from full path/find output

Quick method of isolating filenames from a full path using expansion.

Much quicker than using "basename"


There are 5 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

That's not much quicker than:

echo $(basename $fullpath)

But basename is certainly less cryptic.

Comment by imgx64 248 weeks and 5 days ago

Using "find /" to get all files on my box, it took the expansion version 45 seconds to isolate filenames whilst "basename" took 14 minutes.

That's a hell of a lot quicker.

Comment by quincymd 248 weeks and 5 days ago

AFAIK this "chomp" is builtin - therefore it does not start an extra program - good for scripts... up

Comment by zwergnase 248 weeks and 4 days ago

if you have spaces (evil!) in your filenames, you have to set the IFS to linebreak.

Comment by new_user 248 weeks and 4 days ago


I mean

Comment by new_user 248 weeks and 4 days ago

Yup, that's a "feature" of find we have to work with.

In addition, there are no problems with expansion when reading filenames from a file.

ie find / > tempfile; cat tempfile | while read fullpath; do echo "${fullpath##*/}"; done; rm tempfile

Comment by quincymd 248 weeks and 3 days ago

Your point of view

You must be signed in to comment.