I have a Bash shell script in which I would like to pause execution until the user presses a key. In DOS, this is easily accomplished with the pause
command. Is there a Linux equivalent I can use in my script?
read
does this:
user@host:~$ read -n1 -r -p "Press any key to continue..." key
[...]
user@host:~$
The -n1
specifies that it only waits for a single character. The -r
puts it into raw mode, which is necessary because otherwise, if you press something like backslash, it doesn't register until you hit the next key. The -p
specifies the prompt, which must be quoted if it contains spaces. The key
argument is only necessary if you want to know which key they pressed, in which case you can access it through $key
.
If you are using Bash, you can also specify a timeout with -t
, which causes read to return a failure when a key isn't pressed. So for example:
read -t5 -n1 -r -p 'Press any key in the next five seconds...' key
if [ "$?" -eq "0" ]; then
echo 'A key was pressed.'
else
echo 'No key was pressed.'
fi
Press a key to continue...
then even novice users will be able to find the a
key and press it ;o) –
Fester command | myscript.sh
or myscript.sh | command
. See this answer for a solution. –
Electrodialysis read: 1: read: Illegal option -n
make sure to wrap your command in bash -c 'command && command'
etc. as that error is likely from sh
. I am doing this in a Lando wrapper command. –
Codi I use these ways a lot that are very short, and they are like @theunamedguy and @Jim solutions, but with timeout and silent mode in addition.
I especially love the last case and use it in a lot of scripts that run in a loop until the user presses Enter.
Commands
Enter solution
read -rsp $'Press enter to continue...\n'
Escape solution (with -d $'\e')
read -rsp $'Press escape to continue...\n' -d $'\e'
Any key solution (with -n 1)
read -rsp $'Press any key to continue...\n' -n 1 key # echo $key
Question with preselected choice (with -ei $'Y')
read -rp $'Are you sure (Y/n) : ' -ei $'Y' key; # echo $key
Timeout solution (with -t 5)
read -rsp $'Press any key or wait 5 seconds to continue...\n' -n 1 -t 5;
Sleep enhanced alias
read -rst 0.5; timeout=$? # echo $timeout
Explanation
-r specifies raw mode, which don't allow combined characters like "\" or "^".
-s specifies silent mode, and because we don't need keyboard output.
-p $'prompt' specifies the prompt, which need to be between $' and ' to let spaces and escaped characters. Be careful, you must put between single quotes with dollars symbol to benefit escaped characters, otherwise you can use simple quotes.
-d $'\e' specifies escappe as delimiter charater, so as a final character for current entry, this is possible to put any character but be careful to put a character that the user can type.
-n 1 specifies that it only needs a single character.
-e specifies readline mode.
-i $'Y' specifies Y as initial text in readline mode.
-t 5 specifies a timeout of 5 seconds
key serve in case you need to know the input, in -n1 case, the key that has been pressed.
$? serve to know the exit code of the last program, for read, 142 in case of timeout, 0 correct input. Put $? in a variable as soon as possible if you need to test it after somes commands, because all commands would rewrite $?
-s
; man read
and read --help
help didn't help on Ubuntu 10.04.1 LTS. Edit: help read
did; is the rest deprecated? –
Tokenism read: -i: invalid option
for the ex. read -rp $'Are you sure (Y/n) : ' -ei $'Y' key;
on #osx read -rp $'kill-server: Are you sure (Y/n) : ' -d $'Y' key;
works for me instead. ` –
Kokoschka -i
works perfectly on Ubuntu, also I don't know how if -d
works the same way on OSX. –
Kaon This worked for me on multiple flavors of Linux, where some of these other solutions did not (including the most popular ones here). I think it's more readable too...
echo Press enter to continue; read dummy;
Note that a variable needs to be supplied as an argument to read
.
read
without any parameters will only continue if you press enter.
The DOS pause
command will continue if you press any key. Use read –n1
if you want this behaviour.
read -n1
is not portable. A portable way to do the same might be:
( trap "stty $(stty -g;stty -icanon)" EXIT
LC_ALL=C dd bs=1 count=1 >/dev/null 2>&1
) </dev/tty
Besides using read
, for just a press ENTER
to continue prompt you could do:
sed -n q </dev/tty
status=none
is not portable either. Redirect stdout and stderr to /dev/null instead. read -r line < /dev/tty
would be enought for press ENTER.... –
Syzygy settings=$(stty -g); stty raw; dd ...; stty "$settings"
to save and restore the tty settings. –
Syzygy tr
edit thing could work too? –
Jessy tr
would buffer its output as its a pipe, and non-US keyboards have keys that send characters outside the \1-\177
range. dd
is the idiomatic way here. –
Syzygy dd
's stdin, then you should probably redirect stty
's as well (wrap the whole thing inside {...} < /dev/tty
. Also, like for @Jim's answer, if you want to read all the characters sent upon a key press, you'd need to do something like: (settings=$(stty -g); stty raw min 99 time 1; dd count=1 bs=99 > /dev/null 2>&1; stty "$settings") < /dev/tty
. –
Syzygy raw
implies -isig
which may not be desirable. You might also want to flush the input buffer before issuing the prompt (stty -icanon min 0 time 0; cat > /dev/null
). –
Syzygy stty -icanon min N
- but it might have to wait til i get an actual screen/keyboard. just typing this comment on the tablet is a chore... i think i should be using -icanon
anyway to preserve interrupts. i guess you put in that comment before i could hit submit. we're thinking along the same lines, though, i guess. –
Jessy read -rsp $'Press any key to continue...\n' -n 1 key
before, but it always failed to reset my terminal's settings, so I'd have to run reset
afterwards. This command works perfectly for me (on macOS 10.15)! I also added stty -echo
after the trap
line because I didn't want to see the character I typed. –
Juster If you just need to pause a loop or script, and you're happy to press Enter instead of any key, then read
on its own will do the job.
do_stuff
read
do_more_stuff
It's not end-user friendly, but may be enough in cases where you're writing a quick script for yourself, and you need to pause it to do something manually in the background.
This function works in both bash
and zsh
, and ensures I/O to the terminal:
# Prompt for a keypress to continue. Customise prompt with $*
function pause {
>/dev/tty printf '%s' "${*:-Press any key to continue... }"
[[ $ZSH_VERSION ]] && read -krs # Use -u0 to read from STDIN
[[ $BASH_VERSION ]] && </dev/tty read -rsn1
printf '\n'
}
export_function pause
Put it in your .{ba,z}shrc
for Great Justice!
This fixes it so pressing any key other than ENTER will still go to a new line
read -n1 -r -s -p "Press any key to continue..." ; echo
it's better than windows pause, because you can change the text to make it more useful
read -n1 -r -s -p "Press any key to continue... (cant find the ANY key? press ENTER) " ; echo
.
in the prompt, there is an additional space, for some reason –
Binette system("read -n1 -r -s -p \"Press any key to continue...\" ; echo");
displays an error: sh: 1: read: Illegal option -n
. Though read -n1
command works fine from the same Ubuntu shell. The pause
command can be used as system("pause");
In Windows programs. –
Beatrisbeatrisa Try this:
function pause(){
read -p "$*"
}
Here read
is to read a line of input, and with -p
is to give prompt. And $*
will simply read from args.
How to pass it to script:
./test Some-blah blah with space withoutspace
Now it gets expanded like this:
read -p Some-blah blah with space withoutspace
So in the terminal you will get prompt for Some-blah blah with space withoutspace
, they you can enter your value as response to this prompt.
Yes to using read
- and there are a couple of tweaks that make it most useful in both cron
and in the terminal.
Example:
time rsync (options)
read -n 120 -p "Press 'Enter' to continue..." ; echo " "
The -n 120 makes the read statement time out after 2 minutes so it does not block in cron
.
In terminal it gives 2 minutes to see how long the rsync
command took to execute.
Then the subsequent echo
is so the subsequent bash prompt will appear on the next line.
Otherwise it will show on the same line directly after "continue..." when Enter is pressed in terminal.
© 2022 - 2024 — McMap. All rights reserved.
"Enter any non-NUL character to continue"
. Some keys don't send any character (likeCtrl
...) and some send more than one (likeF1
,Home
...).bash
ignores NUL characters. – Syzygy