4 ms·
The byte that sends SIGQUIT is very much configurable with stty quit ^X , but unfortunately X has to be a-z or one of \]^_ (that is, 0x41 through 0x5F except 0x
by mananaysiempre 2y ago
The byte that sends SIGQUIT is very much configurable with stty quit ^X , but unfortunately X has to be a-z or one of \]^_ (that is, 0x41 through 0x5F except 0x5B = [ which would conflict with other uses of ESC = ^[ = 0x1B) because of how the Ctrl modifier traditionally works. Looking at a map of AZERTY, I don’t see any good options, but you may still want to experiment.
- cperciva 2y agoI map SIGQUIT to ^Q because that's the easiest to remember.
- glandium 2y agoI suppose you never hit CTRL+S by accident?
- cperciva 2y agoRarely enough that needing to open another terminal and use kill to send a signal doesn't bother me.
- kzrdude 2y agostty -ixon Make sure that thing is disabled
- marcosdumay 2y agoI like that Konlose defaults into disabling that thing. And also that there is a visual sign of the terminal being stopped.
- icedchai 2y agoCtrl-S / Ctrl-Q was super useful in the dialup modem days.
- jks 2y agoCuriously, on many terminal emulators the following work: Ctrl-2 = Ctrl-@ = NUL byte Ctrl-3 = Ctrl-[ = ESC Ctrl-4 = Ctrl-\ = default for SIGQUIT Ctrl-5 = Ctrl-] = jump to definition in vim Ctrl-6 = Ctrl-^ = mosh escape key Ctrl-7 = Ctrl-_ = undo in Emacs I think these probably originate in xterm.