8 Mysterious Uses of (!) Operator in Linux Commands

The '!' symbol or operator in Linux can be used as a Logical Negation operator as well as to fetch commands from history with tweaks or to run previously executed commands with modification.

Most of the following Linux commands usage with '!' symbol can vary between different shells. While the examples I provided are commonly used in the bash shell, some other Linux shells may have different implementations or may not support certain uses of the ‘!’ symbol at all.

Let’s dive into the amazing and mysterious uses of '!' symbol or operator in Linux commands.

1. Run a Command from History Using Command Numbers

You might not be aware of the fact that you can run a command from your history command (already/earlier executed commands). To get started first, find the command number by running the ‘history‘ command.

$ history
Find Last Executed Commands in Linux
Find the Last Executed Commands in Linux

To run a command from history by its command number, you can use the '!' symbol followed by the command number as shown.

$ !1551
Run a Command by Its Command Number
Run a Command by Its Command Number

When you execute the above command, it will run the top command at line number 1551 from your history.

Please note that the actual command number may vary depending on your command history. You can use the history command to view the list of commands along with their line numbers.

2. Run Previously Executed Commands in Linux

You may run those commands which you have run previously by their running sequence the last run command will be represented as -1, the second last as -2, the seventh last as -7, and so on.

For example, if you want to rerun the command that was executed six, eight or tenth commands ago, you can use the !-n, where n is the number of commands back you want to reference.

$ history
$ !-6
$ !-8
$ !-10
Re-run a Command in Linux
Re-run a Command in Linux

3. Pass Previous Command’s Arguments to New Command

I need to list the content of the directory ‘/home/$USER/Binary/firefox‘ so I fired.

$ ls /home/$USER/Binary/firefox

Then I realized that I should have fired ‘ls -l‘ to see which file is executable there. So should I type the whole command again? No, I don’t need it. I just need to carry the last argument to this new command as:

$ ls -l !$

Here !$ will carry arguments passed in the last command to this new command.

Pass Arguments of Last Executed Command to New Command
Pass Arguments of the Last Executed Command to the New Command

4. How to Handle Two or More Arguments in Commands

Let’s say I created a text file 1.txt on the Desktop.

$ touch /home/avi/Desktop/1.txt

and then copy it to ‘/home/avi/Downloads‘ using the complete path on either side with the cp command.

$ cp /home/avi/Desktop/1.txt /home/avi/downloads

Now we have passed two arguments with the cp command. First is ‘/home/avi/Desktop/1.txt‘ and the second is ‘/home/avi/Downloads‘, let’s handle them differently, just execute echo [arguments] to print both arguments differently.

$ echo “1st Argument is : !^”
$ echo “2nd Argument is : !cp:2”

Note 1st argument can be printed as “!^” and the rest of the arguments can be printed by executing “![Name_of_Command]:[Number_of_argument]”.

In the above example, the first command was ‘cp‘ and 2nd argument was needed to print. Hence “!cp:2”, if any command says xyz is run with 5 arguments and you need to get the 4th argument, you may use “!xyz:4”, and use it as you like. All the arguments can be accessed by “!*”.

Handle Two or More Arguments

5. Run Last Commands Based on Specific Keywords

We can execute the last executed commands on the basis of keywords. We can understand it as follows:

$ ls /home > /dev/null				[Command 1]
$ ls -l /home/avi/Desktop > /dev/null		[Command 2]	
$ ls -la /home/avi/Downloads > /dev/null	        [Command 3]
$ ls -lA /usr/bin > /dev/null			[Command 4]

Here we have used the ls command but with different switches and for different folders. Moreover, we have sent to the output of each command to ‘/dev/null‘ to keep the console clean.

Now execute the last run commands on the basis of keywords.

$ ! ls			[Command 1]
$ ! ls -l		[Command 2]	
$ ! ls -la		[Command 3]
$ ! ls -lA		[Command 4]

Check the output and you will be astonished that you are running already executed commands just by ls keywords.

Run Commands Based on Keywords

6. Repeat Last Executed Command in Linux

You can run/alter your last executed command using (!!) operator, which is a shorthand notation that allows you to refer to the previous command executed in the command line.

For example, last day I run a one-liner script to find out the IP address of the Linux machine.

$ ip addr show | grep inet | grep -v 'inet6'| grep -v '127.0.0.1' | awk '{print $2}' | cut -f1 -d/

Then suddenly I figured out that I need to redirect the output of the above script to a file ip.txt, so what should I do? Should I retype the whole command again and redirect the output to a file? Well, an easy solution is to use UP navigation key and add '> ip.txt' to redirect the output to a file.

$ ip addr show | grep inet | grep -v 'inet6'| grep -v '127.0.0.1' | awk '{print $2}' | cut -f1 -d/ > ip.txt

Thanks to the Life Savior UP navigation key here. Now consider the below condition, the next time I run the below one-liner script.

$ ifconfig | grep "inet addr:" | awk '{print $2}' | grep -v '127.0.0.1' | cut -f2 -d:

As soon as I run the script, the bash prompt returned an error with the message “bash: ifconfig: command not found”, it was not difficult for me to guess I run this command as a user where it should be run as root.

So what’s the solution? it is difficult to log in to root and then type the whole command again! Also (UP Navigation Key) in the last example didn’t come to the rescue here. So? we need to call “!!” without quotes, which will call the last command for that user.

$ su -c “!!” root

Here su is the switch user which is the root, -c is to run the specified command as the user and the most important part !! will be replaced by command and the last run command will be substituted here. Yeah! You need to provide a root password.

Repeat Last Executed Command in Linux
Repeat Last Executed Command in Linux

7. Remove Files Except One File Using ‘!’ Operator

In Linux, the ! operator (known as the “bang” operator) is used for history expansion that allows you to refer to previous commands in your command history and perform various operations with them.

To remove all files from a directory except for a specific file (important_file.txt), you can use the rm command with ! operator as shown.

$ rm !(important_file.txt)

To remove all the file types from the folder except the one the extension of which is ‘.pdf‘.

$ $ rm !(*.pdf)

8. Check If a Directory Exists in Linux

Here we will use '! -d' to validate if the directory exists or is not followed by Logical AND Operator (&&) to print that directory does not exist and Logical OR Operator (||) to print the directory is present.

Logic is, when the output of [ ! -d /home/avi/Tecmint ] is 0, it will execute what lies beyond Logical AND else it will go to Logical OR (||) and execute what lies beyond Logical OR.

$ [ ! -d /home/avi/Tecmint ] && printf '\nno such /home/avi/Tecmint directory exist\n' || printf '\n/home/avi/Tecmint directory exist\n'

Similar to the above condition, but here if the desired directory doesn’t exist it will exit the command.

$ [ ! -d /home/avi/Tecmint ] && exit

A general implementation in scripting language where if the desired directory does not exist, it will create one.

[ ! -d /home/avi/Tecmint ] && mkdir /home/avi/Tecmint

That’s all for now. If you know or come across any other use of '!' which is worth knowing, you may like to provide us with your suggestion in the feedback. Keep connected!

If you read this far, tweet to the author to show them you care. Tweet a thanks
Ronav Saive
A Passionate GNU/Linux Enthusiast and Software Developer with over a decade in the field of Linux and Open Source technologies.

Each tutorial at TecMint is created by a team of experienced Linux system administrators so that it meets our high-quality standards.

Join the TecMint Weekly Newsletter (More Than 156,129 Linux Enthusiasts Have Subscribed)
Was this article helpful? Please add a comment or buy me a coffee to show your appreciation.

14 thoughts on “8 Mysterious Uses of (!) Operator in Linux Commands”

  1. If you are using BASH in order to expose the use of !, then you must, at least, clarify that BASH is part of the GNU project not of Linux Kernel, please don’t spread misconception.

    Reply
  2. You might also mention !?

    It finds the last command with its’ string argument. For example, if…
    1013 grep tornado /usr/share/dict/words
    1014 grep hurricane /usr/share/dict/words
    1015 wc -l /usr/share/dict/words

    are all in the history then !?torn will grep for tornado again where !torn would search in vain for a command starting with torn.

    And `wc !?torn?:2` works to select argument two from the command containing tornado and run `wc` on it.

    Reply
  3. I didn’t see a mention of historical context in the article, so I’ll give some here in the comments. This form of history command substitution originated with the C Shell (csh), created by Bill Joy for the BSD flavor of UNIX back in the late 70’s. It was later carried into tcsh, and bash (Bourne-Again SHell).

    Personally, I’ve always preferred the C-shell history substitution mechanism, and never really took to the fc command (that I first encountered in the Korne shell).

    Reply
    • Dear Stephen,
      Thanks for the wonderful piece of Information. Keep connected and keep us aware of such context.

      Reply
  4. 4th command. You can access it much simpler. There are actually regular expressions:
    ^ is at the begging expression
    $ is at the end expression
    :number any number parameter

    Example:
    touch a.txt b.txt c.txt
    echo !^ –> display first parameter
    echo !:1 –> also display first parameter
    echo !:2 –> display second parameter
    echo !:3 –> display third parameter
    echo !$ –> display last (in our case 3th) parameter
    echo !* –> display all parameters

    Reply
    • And we did the same

      echo “1st Argument is : !^”
      $ echo “2nd Argument is : !cp:2”

      echo followed by 1st argument and 2nd argument is just to make the tutorial and command understandable. I have used ‘!^’. ‘!command:number’ as you are suggesting.

      I would like to know if you mean something different?

      Reply
  5. I think (5) works differently than you pointed out, and redirection to devnull hides it, but ZSh still prints the command.
    When you invoke “! ls…”, it always picks the last ls command you executed, just appends your switches at the end (after /dev/null).

    One extra cool thing is the !# operator, which picks arguments from current line. Particularly good if you need to retype long path names you already typed in current line. Just say, for example

    cp /some/long/path/to/file.abc !#:1

    And press tab. It’s going to replace last argument with entire path and file name.

    Reply
    • Tomasz,

      For your first part of feedback: It doesn’t pick the last command executed and just to prove this we have used 4 different switches for same command. ($ ! ls $ ! ls -l $ ! ls -la $ ! ls -lA ). Now you may check it by entering the keywords in any order and in each case it will output the same result.

      As far as it is not working in ZSH as expected, i have already mentioned that it i have tested it on BASH and most of these won’t work in other shell.

      For the second part, what you mentioned is a HASH TAG in Linux Command Line and we have included it in one of our article. You may like to read it here: https://www.tecmint.com/linux-commandline-chat-server-and-remove-unwanted-packages/

      Reply
  6. Great post. Thanks, I’ve reshared it to G+

    One note, “su” stands for “switch user” not “Suitable User”. Minor note.
    At least that’s still representative of what it actually does, unlike when most people refer to it as “Super User”, thinking it only grants root user status, which is utterly incorrect.

    Reply

Got something to say? Join the discussion.

Thank you for taking the time to share your thoughts with us. We appreciate your decision to leave a comment and value your contribution to the discussion. It's important to note that we moderate all comments in accordance with our comment policy to ensure a respectful and constructive conversation.

Rest assured that your email address will remain private and will not be published or shared with anyone. We prioritize the privacy and security of our users.