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

change up n directories

Terminal - change up n directories
up () { if [ "${1/[^0-9]/}" == "$1" ]; then p=./; for i in $(seq 1 $1); do p=${p}../; done; cd $p; else echo 'usage: up N'; fi }
2012-04-19 08:16:34
Functions: cd echo seq
2
change up n directories

Change n directories up, without parameters change one up

Alternatives

There are 4 alternatives - vote for the best!

Terminal - Alternatives
up() { local x='';for i in $(seq ${1:-1});do x="$x../"; done;cd $x; }
2012-05-16 04:21:41
User: evil
Functions: cd seq
Tags: cd
8

I wrote this a long time ago, wondering why this wasn't floating around somewhere out there (at least not where I could find).. this seems much more simple than multiple aliases and can cd out of directories easier.

up() { [ $(( $1 + 0 )) -gt 0 ] && cd $(eval "printf '../'%.0s {1..$1}"); }
2012-06-15 17:10:45
User: Mozai
Functions: cd eval
Tags: bash cd
6

`up 3` will climb the directory tree by three steps. `up asdf` will do nothing, and returns exit code 1 as an error should.

Know a better way?

If you can do better, submit your command here.

What others think

I like your numeric test, but I can still save you a few characters...

If you reverse the shell replace, it becomes shorter:

if [ -z "$1//[0-9]/" ]; then

Next, you need to initialise p, but empty is fine

p=;

My final suggestion makes the command longer :-0, but it avoids using seq (making it faster)

for ((i=0;i<${1:-1};i++)); do

That leaves:

up() { if [ -z "${1//[0-9]/}" ]; then p=; for ((i=0;i<${1:-1};i++)); do p=${p}../; done; cd $p; else echo 'usage: up N'; fi }
Comment by flatcap 130 weeks and 3 days ago

Nice modified, flatcap!

I like your shorter numeric test and the default $1 value (1) in the for-loop.

But I think it's better to keep p=./; rather p=;

Because it will cd to $HOME, if you type "$ up 0".

I think keep "$ up 0" in current directory is better. (maybe)

Comment by goldie 130 weeks and 2 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts