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

Ask user to confirm

Terminal - Ask user to confirm
Confirm() { read -sn 1 -p "$1 [Y/N]? "; [[ $REPLY = [Yy] ]]; }
2010-11-22 11:01:14
User: frans
Functions: read
11
Ask user to confirm

Returns true if user presses the key.

Use it like

Confirm "Continue" && do action

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives
Confirm() { echo -n "$1 [y/n]? " ; read reply; case $reply in Y*|y*) true ;; *) false ;; esac }
2010-11-22 16:54:16
User: eikenberry
Functions: echo false read true
Tags: read
2

This version works across on all POSIX compliant shell variants.

Know a better way?

If you can do better, submit your command here.

What others think

It's usually good UI to display the response so the user can confirm that he really did press the wrong key so I would recommend leaving of the -s.

If you'd like to have an echo after the prompt so the next output is not on the same line as the prompt, you can do one of these:

confirm() { read -n 1 -p "$1 [Y/N]? "; [[ $REPLY = [Yy] ]] && echo || { echo; return 1;} } confirm() { read -n 1 -p "$1 [Y/N]? "; [[ $REPLY = [Yy] ]]; local r=$?; echo; return $r; }
Comment by dennisw 212 weeks ago

The fact is that in scripts where i used that, i used the verbosity of the involved action like:

Confirm "Delete files" && rm -v $Files || echo "cancelled"
Comment by frans 212 weeks ago

how do i halt the script if user pressed N at

Confirm() { read -sn 1 -p "$1 [Y/N]? "; [[ $REPLY = [Yy] ]]; } Confirm "Continue?"
Comment by rubo77 158 weeks and 5 days ago

if you mean 'exit', then it's simply:

Confirm "Continue" || exit

The "?" is already in the function so there's no need to pass it in the parameter.

Comment by frans 158 weeks and 5 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts