Hide

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.

Hide

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:

Hide

News

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.
Hide

Tags

Hide

Functions

cd into another dir to run a one-liner, but implicitly drop back to your $OLD_PWD after

Terminal - cd into another dir to run a one-liner, but implicitly drop back to your $OLD_PWD after
( cd $DIR; command; )
2011-03-29 13:16:00
User: sanmiguel
Functions: cd
3
cd into another dir to run a one-liner, but implicitly drop back to your $OLD_PWD after

Obviously the example given is necessarily simple, but this command not only saves time on the command line (saves you using "cd -" or, worse, having to type a fully qualified path if your command cd's more than once), but is vital in scripts, where I've found the behaviour of "cd -" to be a little broken at times.

Alternatives

There are 5 alternatives - vote for the best!

Terminal - Alternatives
(cd /tmp && ls)
cd /path/to/dir && command_or_script; cd -;
pushd /path/to/dir ; command_to_execute; popd

Know a better way?

If you can do better, submit your command here.

What others think

For more complicated tasks you can use

$SHELL

You can then do whatever you like (this includes changing directories as often as you like) and if you are done, you simply use Control-D or

exit

to leave the shell. This not only brings you back into the original directory but also discards settings made by the 'set' command. While $SHELL is supposed to contain the shell you are currently using, you could as well use an alternative shell.

Comment by penpen 160 weeks and 1 day ago

Sorry man but that's a dup of http://www.commandlinefu.com/commands/view/25/jump-to-a-directory-execute-a-command-and-jump-back-to-current-dir so a not a hero anymore (because you didn't use search?)

2penpen

new shell instance is not elegant solution ever. there is no any magic in it

Comment by zolden 160 weeks ago

@zolden: good point. I did search but since that command is so generic, and wasn't tagged, I didn't find it. Apologies for the dupe. Oddly it doesn't show up in the dynamic results dropdown when searching for "(cd", but is the first result if you actually go to the full results list...

@penpen: using $SHELL does pretty much the same thing, except it's a full interactive shell, not a simpler one-liner to immediately drop you back with no extra input...

Comment by sanmiguel 158 weeks and 2 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts