echo '!'whammy

use a literal bang (exclamation point) in a command

Seems obvious, but other seemingly simple ways to use it don't work: echo !whammy and echo "!whammy" both output: -bash: !whammy: event not found and this: echo "\!whammy" outputs: \!whammy with the slash :( you can also do any combinations of quotes for a complex string: echo "It's great to be able to use a bang ("'!'") in a command"'!' outputs: It's great to be able to use a bang (!) in a command!
Sample Output

2009-03-26 23:34:33

These Might Interest You

  • Just feed classical duckduckgo request replacing the "!" for the bang by a "-" (ie. "ddg -gi mickey mouse") and the result will be opened in w3m (think of installing w3m-img for image support in xterm or tty) To put it in the .bashrc, remove the "\" that escapes the "!".

    ddg(){ search=""; bang=""; for term in $@; do if [[ "$term" =~ -([A-Za-z0-9._%+-]*) ]]; then bang="\!${BASH_REMATCH[1]}" ; else search="$search%20$term" ; fi ; done ; w3m "$bang$search" ;}
    boustrophedon757 · 2013-10-30 21:41:36 0
  • Shows "Bang!" in a chance of 1 out of 6, like in the original game with the gun (spin every round). Otherwise, echoes "Click...". If feeling brave you can also do: [ $[ $RANDOM % 6 ] == 0 ] && echo 'Bang!' && a really killer command || echo 'Click...' Show Sample Output

    [ $[ $RANDOM % 6 ] == 0 ] && echo 'Bang!' || echo 'Click...'
    paulera · 2016-03-23 11:09:56 0
  • Use if you want to include untrusted literal strings in your grep regexes. I use it to list all mounts below a directory: dir=/mnt/gentoo; cat /proc/mounts |awk '{print $2}' |egrep "^$(egrep_escape "$dir")(/|$)" /mnt/gentoo /mnt/gentoo/proc /mnt/gentoo/sys /mnt/gentoo/dev /mnt/gentoo/home Works even if $dir contains dangerous characters (e.g. comes from a commandline argument). Show Sample Output

    egrep_escape() { echo "$1" |sed -re 's/([\\.*+?(|)^$[])/\\\1/g' -e 's/\{/[{]/g'; }
    regnarg · 2012-08-02 16:54:43 0
  • Adding the exclamation mark to the image geometry ignores the original aspect ratio. More info about image geometry:

    convert example.png -resize 100x100! output.png
    karpoke · 2010-08-08 17:29:36 0
  • mkdir local-mount-point sshfs user@host:/path/to/remote/dir local-mount-point diff -r /path/to/local/dir local-mount-point fusermount -u local-mount-point # to unmount

    sshfs user@host:/path/to/remote/dir local-mount-point
    okedialf · 2012-10-05 22:10:33 0
  • is great but has a few bugs when people are submitting new commands: . 1. There is no preview button. This was a minor inconvenience before, but now is a major problem since new commands won't show up to be edited until they have been moderated. . 2. White space in the description field and in the comments is almost completely lost. People resort to using periods in between paragraphs to force a line break. Indentation of code is ridiculous. . 3. Many characters get munged. . 3a. For example, a less than character in the description gets read as an HTML tag and discarded. In order to type a less than, I've had to type "<" (I hope that comes out right). Unfortunately, when re-editing a command, the HTML entity is turned into a literal less than character, which I have to change back by hand before saving. 3b. Some unicode characters work in the description field, but turn into ugly literal HTML strings when put in the sample output or in an additional command using the $ prefix. . For example, here is a unicode character: ❥ Here is the same character after a dollar sign: ❥ . 3c. Some unicode characters don't work anywhere. Bizarrely, it appears to be the most commonly needed ones, such as Latin-1 accented characters. Here are some examples, . Bullet: ?, Center dot: ?, Umlaut u: ?. . 4. Here is an example of the greater than, >, and less than, . 5. Commandlinefu used to abbreviate long descriptions on the front page and had a "more..." button so that people could read the rest if they wanted. That's a good feature as it encourages people to explain their commands more fully. Either, the feature has gone missing, or, perhaps, I was just hallucinating it existed in the first place. If the former, please bring it back, If the latter, please implement this great new feature I just thought up. . 6. Tags cannot include Unicode characters. If you try to type one in, the cursor will just spin and spin as it attempt to look up if that tag exists already. For example, try typing Ctrl+Shift+u 2 7 6 5 SPC as a tag name. Show Sample Output

    echo "?????, these are the umlauted vowels I sing to you. Oh, and sometimes ?, but I don't sing that one cause it doesn't rhyme."
    hackerb9 · 2011-01-05 05:56:20 5

What Others Think

Two other simple solutions: 1. Escape it, but don't put it in double quotes: echo \!whammy 2. Put the whole thing in single quotes: echo '!whammy'
bjimba · 477 weeks and 4 days ago
While we're doing neat echo tricks, here's another: doing multi-line echos: echo "hello world" will fail, resulting in [ hello world ] but doing echo 'hello world' will result in [ hello world ] as expected.
clockworkavian · 477 weeks and 4 days ago
clockworkavian Both of your commands shown do *exactly* what is expected. Single quotes prevent the shell from expanding, modifying, or interpreting the data given to it. Double quotes, or interpolating quotes, do not.
ozymandias · 477 weeks and 4 days ago
@bjimba: Didn't know about #1 thanks\! :) and #2 is implied in my examples, I chose to separate the bang into its own single quotes to emphasize their use (I assume most people use none quotes or double quotes normally, like me.) I don't know why I tend to use double quotes at the shell. Coming from a PHP background, I use single quotes 99% of the time elsewhere. @ozymandias: Thanks for the info, I wish I would have know that all along. It's very similar to the difference between single and doubt quotes in PHP. I'm surprised I didn't make the connection earlier. Makes me glad I posted this one. I learned a lot :)
sudopeople · 477 weeks and 3 days ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. 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.

Share Your Commands

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.


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: