Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #16296 > unrolled thread
| Started by | worley@alum.mit.edu (Dale R. Worley) |
|---|---|
| First post | 2020-05-10 21:50 -0400 |
| Last post | 2020-05-10 21:50 -0400 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: CTRL-C on command line does not cancel current command worley@alum.mit.edu (Dale R. Worley) - 2020-05-10 21:50 -0400
| From | worley@alum.mit.edu (Dale R. Worley) |
|---|---|
| Date | 2020-05-10 21:50 -0400 |
| Subject | Re: CTRL-C on command line does not cancel current command |
| Message-ID | <mailman.2598.1589162343.3066.bug-bash@gnu.org> |
Paul Kelaita <paul@kelaita.com> writes: > Sorry, I'm wondering if I should have taken this to the iSH forums, > but it just seems like a bash issue. You should ask around, because how Ctrl-C cancels input involves the interaction of the OS, the bash code proper, and (I assume) the stdin library. E.g. if the OS doesn't actually deliver the characters to bash until you type RET, then the OS has to take care of clearing the partially-input line. And all of these actions can be modulated by your stty settings and any special input mode(s) that bash activates. Dale
Back to top | Article view | gnu.bash.bug
csiph-web