Is CTRL+C incorrect to use to return to command line? The Next CEO of Stack OverflowWindows shell Escape key (delete whole line) equivalent in BashRemember a half-typed command while I check somethingadvance strategy to interrupt a linux application that has “hung” and made X desktop unresponsiveWindows shell Escape key (delete whole line) equivalent in BashCan I make `rm` interactive only when using globbing? (in either bash or zsh or both)Why does this PS1 value cause unexpected behaviour?Terminal prompt not wrapping correctlyExecute a program at loginWhat is most secure and simplest way to have a user-typed password on bash become part of stdin to a program?Pipe from a while loop to a command but execute another command if pipe command failsWhy don't here strings in Makefiles using Bash work?
Touchpad not working on Debian 9
Where do students learn to solve polynomial equations these days?
Help/tips for a first time writer?
Calculate the Mean mean of two numbers
What flight has the highest ratio of timezone difference to flight time?
Is it ever safe to open a suspicious HTML file (e.g. email attachment)?
Help understanding this unsettling image of Titan, Epimetheus, and Saturn's rings?
Spaces in which all closed sets are regular closed
How to use ReplaceAll on an expression that contains a rule
Is dried pee considered dirt?
Traduction de « Life is a roller coaster »
Is it correct to say moon starry nights?
TikZ: How to fill area with a special pattern?
How to find image of a complex function with given constraints?
What would be the main consequences for a country leaving the WTO?
How to Implement Deterministic Encryption Safely in .NET
Can Sneak Attack be used when hitting with an improvised weapon?
Won the lottery - how do I keep the money?
Is there an equivalent of cd - for cp or mv
How did Beeri the Hittite come up with naming his daughter Yehudit?
What was Carter Burke's job for "the company" in Aliens?
IC has pull-down resistors on SMBus lines?
Reshaping json / reparing json inside shell script (remove trailing comma)
Do scriptures give a method to recognize a truly self-realized person/jivanmukta?
Is CTRL+C incorrect to use to return to command line?
The Next CEO of Stack OverflowWindows shell Escape key (delete whole line) equivalent in BashRemember a half-typed command while I check somethingadvance strategy to interrupt a linux application that has “hung” and made X desktop unresponsiveWindows shell Escape key (delete whole line) equivalent in BashCan I make `rm` interactive only when using globbing? (in either bash or zsh or both)Why does this PS1 value cause unexpected behaviour?Terminal prompt not wrapping correctlyExecute a program at loginWhat is most secure and simplest way to have a user-typed password on bash become part of stdin to a program?Pipe from a while loop to a command but execute another command if pipe command failsWhy don't here strings in Makefiles using Bash work?
When I'm using tail -f and I want to return to the shell, I always use CTRL+C. Or when I am typing a command and feel like aborting it and starting over, I simply CTRL+C to get back to an empty command line prompt. Is this considered bad practice? I sometimes feel there might be a better way to break away from something, but really have no idea.
linux bash
asked Jan 21 '12 at 20:48
useruser
65351528
migrated from serverfault.com Jan 21 '12 at 21:07
This question came from our site for system and network administrators.
add a comment |
When I'm using tail -f and I want to return to the shell, I always use CTRL+C. Or when I am typing a command and feel like aborting it and starting over, I simply CTRL+C to get back to an empty command line prompt. Is this considered bad practice? I sometimes feel there might be a better way to break away from something, but really have no idea.
linux bash
asked Jan 21 '12 at 20:48
useruser
65351528
migrated from serverfault.com Jan 21 '12 at 21:07
This question came from our site for system and network administrators.
6
To cancel a partially entered shell command, you can use Control-U or Delete (depending on your tty settings and key bindings), but there's nothing wrong with using Control-C.
– Keith Thompson
Jan 21 '12 at 20:56
@KeithThompson thanks for the Ctrl+U, I wasnt aware of that one :-)
– Patrick
Jan 21 '12 at 22:47
For the record, C-u doesn't actually cancel the command entered, it moves it to the paste buffer (similar to the "cut" functionality of some programs).
– Chris Down
Nov 9 '12 at 13:43
add a comment |
When I'm using tail -f and I want to return to the shell, I always use CTRL+C. Or when I am typing a command and feel like aborting it and starting over, I simply CTRL+C to get back to an empty command line prompt. Is this considered bad practice? I sometimes feel there might be a better way to break away from something, but really have no idea.
linux bash
asked Jan 21 '12 at 20:48
useruser
65351528
When I'm using tail -f and I want to return to the shell, I always use CTRL+C. Or when I am typing a command and feel like aborting it and starting over, I simply CTRL+C to get back to an empty command line prompt. Is this considered bad practice? I sometimes feel there might be a better way to break away from something, but really have no idea.
linux bash
linux bash
asked Jan 21 '12 at 20:48
useruser
65351528
asked Jan 21 '12 at 20:48
useruser
65351528
asked Jan 21 '12 at 20:48
useruser
65351528
asked Jan 21 '12 at 20:48
useruser
65351528
asked Jan 21 '12 at 20:48
useruser
65351528
65351528
migrated from serverfault.com Jan 21 '12 at 21:07
This question came from our site for system and network administrators.
migrated from serverfault.com Jan 21 '12 at 21:07
This question came from our site for system and network administrators.
6
To cancel a partially entered shell command, you can use Control-U or Delete (depending on your tty settings and key bindings), but there's nothing wrong with using Control-C.
– Keith Thompson
Jan 21 '12 at 20:56
@KeithThompson thanks for the Ctrl+U, I wasnt aware of that one :-)
– Patrick
Jan 21 '12 at 22:47
For the record, C-u doesn't actually cancel the command entered, it moves it to the paste buffer (similar to the "cut" functionality of some programs).
– Chris Down
Nov 9 '12 at 13:43
add a comment |
6
To cancel a partially entered shell command, you can use Control-U or Delete (depending on your tty settings and key bindings), but there's nothing wrong with using Control-C.
– Keith Thompson
Jan 21 '12 at 20:56
@KeithThompson thanks for the Ctrl+U, I wasnt aware of that one :-)
– Patrick
Jan 21 '12 at 22:47
For the record, C-u doesn't actually cancel the command entered, it moves it to the paste buffer (similar to the "cut" functionality of some programs).
– Chris Down
Nov 9 '12 at 13:43
6
6
To cancel a partially entered shell command, you can use Control-U or Delete (depending on your tty settings and key bindings), but there's nothing wrong with using Control-C.
– Keith Thompson
Jan 21 '12 at 20:56
To cancel a partially entered shell command, you can use Control-U or Delete (depending on your tty settings and key bindings), but there's nothing wrong with using Control-C.
– Keith Thompson
Jan 21 '12 at 20:56
@KeithThompson thanks for the Ctrl+U, I wasnt aware of that one :-)
– Patrick
Jan 21 '12 at 22:47
@KeithThompson thanks for the Ctrl+U, I wasnt aware of that one :-)
– Patrick
Jan 21 '12 at 22:47
For the record, C-u doesn't actually cancel the command entered, it moves it to the paste buffer (similar to the "cut" functionality of some programs).
– Chris Down
Nov 9 '12 at 13:43
For the record, C-u doesn't actually cancel the command entered, it moves it to the paste buffer (similar to the "cut" functionality of some programs).
– Chris Down
Nov 9 '12 at 13:43
add a comment |
6 Answers
6
active
oldest
votes
Ctrl+C sends a SIGINT to the program. This tells the program that you want to interrupt (and end) it's process. Most programs correctly catch this and cleanly exit. So, yes, this is a "correct" way to end most programs.
There are other keyboard shortcuts for sending other signals to programs, but this is the most common.
answered Jan 21 '12 at 20:53
Chris SChris S
1,166812
9
There's also Ctrl+D for programs that are reading input from the user. Ctrl+D closes STDIN to the program. For gracefully exiting the shell this is also available (exact same as typing exit).
– Patrick
Jan 21 '12 at 22:48
2
@Patrick Ctrl+D actually sends an End of File indicator to the stream. It's up to the program to respond appropriately (usually closing the file stream).
– Chris S
Jan 22 '12 at 2:32
thats what closing STDIN does. You cant get EOF without the pipe/stream being closed.
– Patrick
Jan 22 '12 at 3:27
9
Wrong on three counts, Patrick. First: Control+D doesn't have this meaning for pipes. Second: the EOF special character doesn't close anything. It causes a one time return of zero bytes (presuming that the line buffer is empty) from the currentread()system call. The nextread()s are unaffected. Third: None of this applies to programs which put the line discipline into non-canonical mode, such as most shell programs from the past couple of decades and indeed any other program that uses a library such as GNUreadline.
– JdeBP
Jan 22 '12 at 11:32
add a comment |
This method is just fine, really.
answered Jan 21 '12 at 20:52
SvenSven
2,0071214
add a comment |
To abort a long command while typing, I sometimes jump to the start of line, and insert a comment sign, before hitting enter:
Home#Enter
Pos1#Return
This is useful, if I typed a copy command with a long path, for example, and meanwhile observe, that I first need to create the directory, but would like to repeat the command afterwards. Then I just have to take it from the history, delete the hash, and enter it.
In Bash, you can use the shortcut
Alt+#
to remarkify your command, as pointed out in the comments (Thanks, @Zorawar).
answered Jan 22 '12 at 2:01
user unknownuser unknown
7,44112450
6
You can also useCtrl-Awithout taking your fingers off the home row.
– Dietrich Epp
Jan 22 '12 at 3:30
1
AndCtrl-Egoes to the end, by the way.
– Dave
Jan 27 '12 at 18:15
@Dave: That's right, but you don't need to move to the end to hit enter, to confirm your command. The commandline is not an editor, where this might insert a newline.
– user unknown
Jan 27 '12 at 20:12
2
In bash you can achieve the same thing by just pressingAlt-#: it will put the comment in and run the command (so putting it in your history).
– Zorawar
Jun 6 '15 at 14:50
add a comment |
Generally speaking, using Ctrl+C is fine when the program offers you no interactive way to terminate (either by design, or, more frequently, because it has frozen or become unusable). Just bear in mind that, when in interactive mode, the key combo you really want may be Ctrl+D, which sends an EOF, signaling the end of the input.
edited Jan 26 '12 at 1:37
Kevin
27.8k1066103
answered Jan 21 '12 at 21:32
ZorawarZorawar
500212
add a comment |
If using Bash, one can also use Ctrl-Z, and type bg to "put the current job in background".
answered Jan 26 '12 at 19:53
ComputistComputist
1113
add a comment |
As @Patrick said in the comment on the accepted answer,
There's also
Ctrl+Dfor programs that are reading input from the user.Ctrl+Dcloses STDIN to the program.
This helped me when Ctrl+C did not work to get the command line back after using >>
answered 2 days ago
enharmonicenharmonic
1
New contributor
enharmonic is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f29654%2fis-ctrlc-incorrect-to-use-to-return-to-command-line%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
6 Answers
6
active
oldest
votes
6 Answers
6
active
oldest
votes
active
oldest
votes
active
oldest
votes
Ctrl+C sends a SIGINT to the program. This tells the program that you want to interrupt (and end) it's process. Most programs correctly catch this and cleanly exit. So, yes, this is a "correct" way to end most programs.
There are other keyboard shortcuts for sending other signals to programs, but this is the most common.
answered Jan 21 '12 at 20:53
Chris SChris S
1,166812
9
There's also Ctrl+D for programs that are reading input from the user. Ctrl+D closes STDIN to the program. For gracefully exiting the shell this is also available (exact same as typing exit).
– Patrick
Jan 21 '12 at 22:48
2
@Patrick Ctrl+D actually sends an End of File indicator to the stream. It's up to the program to respond appropriately (usually closing the file stream).
– Chris S
Jan 22 '12 at 2:32
thats what closing STDIN does. You cant get EOF without the pipe/stream being closed.
– Patrick
Jan 22 '12 at 3:27
9
Wrong on three counts, Patrick. First: Control+D doesn't have this meaning for pipes. Second: the EOF special character doesn't close anything. It causes a one time return of zero bytes (presuming that the line buffer is empty) from the currentread()system call. The nextread()s are unaffected. Third: None of this applies to programs which put the line discipline into non-canonical mode, such as most shell programs from the past couple of decades and indeed any other program that uses a library such as GNUreadline.
– JdeBP
Jan 22 '12 at 11:32
add a comment |
Ctrl+C sends a SIGINT to the program. This tells the program that you want to interrupt (and end) it's process. Most programs correctly catch this and cleanly exit. So, yes, this is a "correct" way to end most programs.
There are other keyboard shortcuts for sending other signals to programs, but this is the most common.
answered Jan 21 '12 at 20:53
Chris SChris S
1,166812
9
There's also Ctrl+D for programs that are reading input from the user. Ctrl+D closes STDIN to the program. For gracefully exiting the shell this is also available (exact same as typing exit).
– Patrick
Jan 21 '12 at 22:48
2
@Patrick Ctrl+D actually sends an End of File indicator to the stream. It's up to the program to respond appropriately (usually closing the file stream).
– Chris S
Jan 22 '12 at 2:32
thats what closing STDIN does. You cant get EOF without the pipe/stream being closed.
– Patrick
Jan 22 '12 at 3:27
9
Wrong on three counts, Patrick. First: Control+D doesn't have this meaning for pipes. Second: the EOF special character doesn't close anything. It causes a one time return of zero bytes (presuming that the line buffer is empty) from the currentread()system call. The nextread()s are unaffected. Third: None of this applies to programs which put the line discipline into non-canonical mode, such as most shell programs from the past couple of decades and indeed any other program that uses a library such as GNUreadline.
– JdeBP
Jan 22 '12 at 11:32
add a comment |
Ctrl+C sends a SIGINT to the program. This tells the program that you want to interrupt (and end) it's process. Most programs correctly catch this and cleanly exit. So, yes, this is a "correct" way to end most programs.
There are other keyboard shortcuts for sending other signals to programs, but this is the most common.
answered Jan 21 '12 at 20:53
Chris SChris S
1,166812
Ctrl+C sends a SIGINT to the program. This tells the program that you want to interrupt (and end) it's process. Most programs correctly catch this and cleanly exit. So, yes, this is a "correct" way to end most programs.
There are other keyboard shortcuts for sending other signals to programs, but this is the most common.
answered Jan 21 '12 at 20:53
Chris SChris S
1,166812
answered Jan 21 '12 at 20:53
Chris SChris S
1,166812
answered Jan 21 '12 at 20:53
Chris SChris S
1,166812
answered Jan 21 '12 at 20:53
Chris SChris S
1,166812
1,166812
9
There's also Ctrl+D for programs that are reading input from the user. Ctrl+D closes STDIN to the program. For gracefully exiting the shell this is also available (exact same as typing exit).
– Patrick
Jan 21 '12 at 22:48
2
@Patrick Ctrl+D actually sends an End of File indicator to the stream. It's up to the program to respond appropriately (usually closing the file stream).
– Chris S
Jan 22 '12 at 2:32
thats what closing STDIN does. You cant get EOF without the pipe/stream being closed.
– Patrick
Jan 22 '12 at 3:27
9
Wrong on three counts, Patrick. First: Control+D doesn't have this meaning for pipes. Second: the EOF special character doesn't close anything. It causes a one time return of zero bytes (presuming that the line buffer is empty) from the currentread()system call. The nextread()s are unaffected. Third: None of this applies to programs which put the line discipline into non-canonical mode, such as most shell programs from the past couple of decades and indeed any other program that uses a library such as GNUreadline.
– JdeBP
Jan 22 '12 at 11:32
add a comment |
9
There's also Ctrl+D for programs that are reading input from the user. Ctrl+D closes STDIN to the program. For gracefully exiting the shell this is also available (exact same as typing exit).
– Patrick
Jan 21 '12 at 22:48
2
@Patrick Ctrl+D actually sends an End of File indicator to the stream. It's up to the program to respond appropriately (usually closing the file stream).
– Chris S
Jan 22 '12 at 2:32
thats what closing STDIN does. You cant get EOF without the pipe/stream being closed.
– Patrick
Jan 22 '12 at 3:27
9
Wrong on three counts, Patrick. First: Control+D doesn't have this meaning for pipes. Second: the EOF special character doesn't close anything. It causes a one time return of zero bytes (presuming that the line buffer is empty) from the currentread()system call. The nextread()s are unaffected. Third: None of this applies to programs which put the line discipline into non-canonical mode, such as most shell programs from the past couple of decades and indeed any other program that uses a library such as GNUreadline.
– JdeBP
Jan 22 '12 at 11:32
9
9
There's also Ctrl+D for programs that are reading input from the user. Ctrl+D closes STDIN to the program. For gracefully exiting the shell this is also available (exact same as typing exit).
– Patrick
Jan 21 '12 at 22:48
There's also Ctrl+D for programs that are reading input from the user. Ctrl+D closes STDIN to the program. For gracefully exiting the shell this is also available (exact same as typing exit).
– Patrick
Jan 21 '12 at 22:48
2
2
@Patrick Ctrl+D actually sends an End of File indicator to the stream. It's up to the program to respond appropriately (usually closing the file stream).
– Chris S
Jan 22 '12 at 2:32
@Patrick Ctrl+D actually sends an End of File indicator to the stream. It's up to the program to respond appropriately (usually closing the file stream).
– Chris S
Jan 22 '12 at 2:32
thats what closing STDIN does. You cant get EOF without the pipe/stream being closed.
– Patrick
Jan 22 '12 at 3:27
thats what closing STDIN does. You cant get EOF without the pipe/stream being closed.
– Patrick
Jan 22 '12 at 3:27
9
9
Wrong on three counts, Patrick. First: Control+D doesn't have this meaning for pipes. Second: the EOF special character doesn't close anything. It causes a one time return of zero bytes (presuming that the line buffer is empty) from the current
read() system call. The next read()s are unaffected. Third: None of this applies to programs which put the line discipline into non-canonical mode, such as most shell programs from the past couple of decades and indeed any other program that uses a library such as GNU readline.– JdeBP
Jan 22 '12 at 11:32
Wrong on three counts, Patrick. First: Control+D doesn't have this meaning for pipes. Second: the EOF special character doesn't close anything. It causes a one time return of zero bytes (presuming that the line buffer is empty) from the current
read() system call. The next read()s are unaffected. Third: None of this applies to programs which put the line discipline into non-canonical mode, such as most shell programs from the past couple of decades and indeed any other program that uses a library such as GNU readline.– JdeBP
Jan 22 '12 at 11:32
add a comment |
This method is just fine, really.
answered Jan 21 '12 at 20:52
SvenSven
2,0071214
add a comment |
This method is just fine, really.
answered Jan 21 '12 at 20:52
SvenSven
2,0071214
add a comment |
This method is just fine, really.
answered Jan 21 '12 at 20:52
SvenSven
2,0071214
This method is just fine, really.
answered Jan 21 '12 at 20:52
SvenSven
2,0071214
answered Jan 21 '12 at 20:52
SvenSven
2,0071214
answered Jan 21 '12 at 20:52
SvenSven
2,0071214
answered Jan 21 '12 at 20:52
SvenSven
2,0071214
2,0071214
add a comment |
add a comment |
To abort a long command while typing, I sometimes jump to the start of line, and insert a comment sign, before hitting enter:
Home#Enter
Pos1#Return
This is useful, if I typed a copy command with a long path, for example, and meanwhile observe, that I first need to create the directory, but would like to repeat the command afterwards. Then I just have to take it from the history, delete the hash, and enter it.
In Bash, you can use the shortcut
Alt+#
to remarkify your command, as pointed out in the comments (Thanks, @Zorawar).
answered Jan 22 '12 at 2:01
user unknownuser unknown
7,44112450
6
You can also useCtrl-Awithout taking your fingers off the home row.
– Dietrich Epp
Jan 22 '12 at 3:30
1
AndCtrl-Egoes to the end, by the way.
– Dave
Jan 27 '12 at 18:15
@Dave: That's right, but you don't need to move to the end to hit enter, to confirm your command. The commandline is not an editor, where this might insert a newline.
– user unknown
Jan 27 '12 at 20:12
2
In bash you can achieve the same thing by just pressingAlt-#: it will put the comment in and run the command (so putting it in your history).
– Zorawar
Jun 6 '15 at 14:50
add a comment |
To abort a long command while typing, I sometimes jump to the start of line, and insert a comment sign, before hitting enter:
Home#Enter
Pos1#Return
This is useful, if I typed a copy command with a long path, for example, and meanwhile observe, that I first need to create the directory, but would like to repeat the command afterwards. Then I just have to take it from the history, delete the hash, and enter it.
In Bash, you can use the shortcut
Alt+#
to remarkify your command, as pointed out in the comments (Thanks, @Zorawar).
answered Jan 22 '12 at 2:01
user unknownuser unknown
7,44112450
6
You can also useCtrl-Awithout taking your fingers off the home row.
– Dietrich Epp
Jan 22 '12 at 3:30
1
AndCtrl-Egoes to the end, by the way.
– Dave
Jan 27 '12 at 18:15
@Dave: That's right, but you don't need to move to the end to hit enter, to confirm your command. The commandline is not an editor, where this might insert a newline.
– user unknown
Jan 27 '12 at 20:12
2
In bash you can achieve the same thing by just pressingAlt-#: it will put the comment in and run the command (so putting it in your history).
– Zorawar
Jun 6 '15 at 14:50
add a comment |
To abort a long command while typing, I sometimes jump to the start of line, and insert a comment sign, before hitting enter:
Home#Enter
Pos1#Return
This is useful, if I typed a copy command with a long path, for example, and meanwhile observe, that I first need to create the directory, but would like to repeat the command afterwards. Then I just have to take it from the history, delete the hash, and enter it.
In Bash, you can use the shortcut
Alt+#
to remarkify your command, as pointed out in the comments (Thanks, @Zorawar).
answered Jan 22 '12 at 2:01
user unknownuser unknown
7,44112450
To abort a long command while typing, I sometimes jump to the start of line, and insert a comment sign, before hitting enter:
Home#Enter
Pos1#Return
This is useful, if I typed a copy command with a long path, for example, and meanwhile observe, that I first need to create the directory, but would like to repeat the command afterwards. Then I just have to take it from the history, delete the hash, and enter it.
In Bash, you can use the shortcut
Alt+#
to remarkify your command, as pointed out in the comments (Thanks, @Zorawar).
answered Jan 22 '12 at 2:01
user unknownuser unknown
7,44112450
edited Feb 28 '17 at 0:19
answered Jan 22 '12 at 2:01
user unknownuser unknown
7,44112450
answered Jan 22 '12 at 2:01
user unknownuser unknown
7,44112450
answered Jan 22 '12 at 2:01
user unknownuser unknown
7,44112450
7,44112450
6
You can also useCtrl-Awithout taking your fingers off the home row.
– Dietrich Epp
Jan 22 '12 at 3:30
1
AndCtrl-Egoes to the end, by the way.
– Dave
Jan 27 '12 at 18:15
@Dave: That's right, but you don't need to move to the end to hit enter, to confirm your command. The commandline is not an editor, where this might insert a newline.
– user unknown
Jan 27 '12 at 20:12
2
In bash you can achieve the same thing by just pressingAlt-#: it will put the comment in and run the command (so putting it in your history).
– Zorawar
Jun 6 '15 at 14:50
add a comment |
6
You can also useCtrl-Awithout taking your fingers off the home row.
– Dietrich Epp
Jan 22 '12 at 3:30
1
AndCtrl-Egoes to the end, by the way.
– Dave
Jan 27 '12 at 18:15
@Dave: That's right, but you don't need to move to the end to hit enter, to confirm your command. The commandline is not an editor, where this might insert a newline.
– user unknown
Jan 27 '12 at 20:12
2
In bash you can achieve the same thing by just pressingAlt-#: it will put the comment in and run the command (so putting it in your history).
– Zorawar
Jun 6 '15 at 14:50
6
6
You can also use
Ctrl-A without taking your fingers off the home row.– Dietrich Epp
Jan 22 '12 at 3:30
You can also use
Ctrl-A without taking your fingers off the home row.– Dietrich Epp
Jan 22 '12 at 3:30
1
1
And
Ctrl-E goes to the end, by the way.– Dave
Jan 27 '12 at 18:15
And
Ctrl-E goes to the end, by the way.– Dave
Jan 27 '12 at 18:15
@Dave: That's right, but you don't need to move to the end to hit enter, to confirm your command. The commandline is not an editor, where this might insert a newline.
– user unknown
Jan 27 '12 at 20:12
@Dave: That's right, but you don't need to move to the end to hit enter, to confirm your command. The commandline is not an editor, where this might insert a newline.
– user unknown
Jan 27 '12 at 20:12
2
2
In bash you can achieve the same thing by just pressing
Alt-#: it will put the comment in and run the command (so putting it in your history).– Zorawar
Jun 6 '15 at 14:50
In bash you can achieve the same thing by just pressing
Alt-#: it will put the comment in and run the command (so putting it in your history).– Zorawar
Jun 6 '15 at 14:50
add a comment |
Generally speaking, using Ctrl+C is fine when the program offers you no interactive way to terminate (either by design, or, more frequently, because it has frozen or become unusable). Just bear in mind that, when in interactive mode, the key combo you really want may be Ctrl+D, which sends an EOF, signaling the end of the input.
edited Jan 26 '12 at 1:37
Kevin
27.8k1066103
answered Jan 21 '12 at 21:32
ZorawarZorawar
500212
add a comment |
Generally speaking, using Ctrl+C is fine when the program offers you no interactive way to terminate (either by design, or, more frequently, because it has frozen or become unusable). Just bear in mind that, when in interactive mode, the key combo you really want may be Ctrl+D, which sends an EOF, signaling the end of the input.
edited Jan 26 '12 at 1:37
Kevin
27.8k1066103
answered Jan 21 '12 at 21:32
ZorawarZorawar
500212
add a comment |
Generally speaking, using Ctrl+C is fine when the program offers you no interactive way to terminate (either by design, or, more frequently, because it has frozen or become unusable). Just bear in mind that, when in interactive mode, the key combo you really want may be Ctrl+D, which sends an EOF, signaling the end of the input.
edited Jan 26 '12 at 1:37
Kevin
27.8k1066103
answered Jan 21 '12 at 21:32
ZorawarZorawar
500212
Generally speaking, using Ctrl+C is fine when the program offers you no interactive way to terminate (either by design, or, more frequently, because it has frozen or become unusable). Just bear in mind that, when in interactive mode, the key combo you really want may be Ctrl+D, which sends an EOF, signaling the end of the input.
edited Jan 26 '12 at 1:37
Kevin
27.8k1066103
answered Jan 21 '12 at 21:32
ZorawarZorawar
500212
edited Jan 26 '12 at 1:37
Kevin
27.8k1066103
edited Jan 26 '12 at 1:37
Kevin
27.8k1066103
edited Jan 26 '12 at 1:37
Kevin
27.8k1066103
27.8k1066103
answered Jan 21 '12 at 21:32
ZorawarZorawar
500212
answered Jan 21 '12 at 21:32
ZorawarZorawar
500212
answered Jan 21 '12 at 21:32
ZorawarZorawar
500212
500212
add a comment |
add a comment |
If using Bash, one can also use Ctrl-Z, and type bg to "put the current job in background".
answered Jan 26 '12 at 19:53
ComputistComputist
1113
add a comment |
If using Bash, one can also use Ctrl-Z, and type bg to "put the current job in background".
answered Jan 26 '12 at 19:53
ComputistComputist
1113
add a comment |
If using Bash, one can also use Ctrl-Z, and type bg to "put the current job in background".
answered Jan 26 '12 at 19:53
ComputistComputist
1113
If using Bash, one can also use Ctrl-Z, and type bg to "put the current job in background".
answered Jan 26 '12 at 19:53
ComputistComputist
1113
answered Jan 26 '12 at 19:53
ComputistComputist
1113
answered Jan 26 '12 at 19:53
ComputistComputist
1113
answered Jan 26 '12 at 19:53
ComputistComputist
1113
1113
add a comment |
add a comment |
As @Patrick said in the comment on the accepted answer,
There's also
Ctrl+Dfor programs that are reading input from the user.Ctrl+Dcloses STDIN to the program.
This helped me when Ctrl+C did not work to get the command line back after using >>
answered 2 days ago
enharmonicenharmonic
1
New contributor
enharmonic is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
As @Patrick said in the comment on the accepted answer,
There's also
Ctrl+Dfor programs that are reading input from the user.Ctrl+Dcloses STDIN to the program.
This helped me when Ctrl+C did not work to get the command line back after using >>
answered 2 days ago
enharmonicenharmonic
1
New contributor
enharmonic is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
As @Patrick said in the comment on the accepted answer,
There's also
Ctrl+Dfor programs that are reading input from the user.Ctrl+Dcloses STDIN to the program.
This helped me when Ctrl+C did not work to get the command line back after using >>
answered 2 days ago
enharmonicenharmonic
1
New contributor
enharmonic is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
As @Patrick said in the comment on the accepted answer,
There's also
Ctrl+Dfor programs that are reading input from the user.Ctrl+Dcloses STDIN to the program.
This helped me when Ctrl+C did not work to get the command line back after using >>
answered 2 days ago
enharmonicenharmonic
1
New contributor
enharmonic is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 days ago
enharmonicenharmonic
1
New contributor
enharmonic is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 days ago
enharmonicenharmonic
1
answered 2 days ago
enharmonicenharmonic
1
1
New contributor
enharmonic is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
enharmonic is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
enharmonic is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f29654%2fis-ctrlc-incorrect-to-use-to-return-to-command-line%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
6
To cancel a partially entered shell command, you can use Control-U or Delete (depending on your tty settings and key bindings), but there's nothing wrong with using Control-C.
– Keith Thompson
Jan 21 '12 at 20:56
@KeithThompson thanks for the Ctrl+U, I wasnt aware of that one :-)
– Patrick
Jan 21 '12 at 22:47
For the record, C-u doesn't actually cancel the command entered, it moves it to the paste buffer (similar to the "cut" functionality of some programs).
– Chris Down
Nov 9 '12 at 13:43