Bug 306982

Summary:	Mismanagement of keys for suspending output - allow changing of keys
Product:	[Applications] konsole	Reporter:	Ganton <kubry>
Component:	general	Assignee:	Konsole Bugs <konsole-bugs-null>
Status:	CONFIRMED ---
Severity:	wishlist	CC:	cpigat242, kdebugs
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Ganton 2012-09-18 13:43:29 UTC

Usually, Ctrl+S suspends output in Konsole. So, when pressing Ctrl+S, Konsole says "Output has been suspended by pressing Ctrl+S. [...]".

But many times it's another key (for example Ctrl+X) that suspends output, but Konsole keeps saying "Output has been suspended by pressing Ctrl+S. [...]" when Ctrl+S has been pressed... but the output has not been suspended (because, for example, Ctrl+X has not been pressed).

"Ctrl+S" should not be a "fixed value" in Konsole. A person can find out which is the "key to suspend output" executing "stty -a". For example "stty -a" can return "[...] stop = ^S [...]" which means that Ctrl+S is the suspending key; in another case,  "stty -a" can return "[...] stop = ^X [...]", etc. Konsole could find out which is the key to suspend output, instead of always saying "Ctrl+S".

[A little off-topic: A usual reason for changing the behaviour of Ctrl+S is that Ctrl+S is the default BASH key binding for incremental history search forward. So, that key binding is shadowed by so called terminal flow control key binding. We can find out more in http://ruslanspivak.com/2010/11/25/bash-history-incremental-search-forward/]


Reproducible: Always

Steps to Reproduce:
1. In Konsole, execute:    stty stop ^X
2. Press Ctrl+S

Actual Results:  
See how Konsole says "Output has been suspended by pressing Ctrl+S. [...]" but the output has not been suspended, you can press Ctrl+G and keep on writing.

Expected Results:  
Konsole should not have said anything. 

However, if the user had pressed Ctr+X, Konsole could have said "Output has been suspended by pressing Ctrl+X. Press [...]"

Comment 1 Jekyll Wu 2012-09-21 11:53:23 UTC

Thanks for reporting. Yes, konsole currently only detects hardcoded Ctrl+S and Ctrl+Q

Comment 2 Kurt Hindenburg 2012-09-23 14:30:20 UTC

This shouldn't be hard to fix - let me try to get something coded


kDebug()<<ttmode.c_cc[VSTOP];
kDebug()<<ttmode.c_cc[VSTART];

Comment 3 sparhawk 2013-01-20 09:06:31 UTC

This bug probably also relates to this request [1] to allow the user to swap Ctrl+C (SIGINT) and Shift+Ctrl+C (copy), as per Guake and gnome-terminal.

[1] https://bugs.kde.org/show_bug.cgi?id=311617

Comment 4 Kurt Hindenburg 2017-02-13 01:57:01 UTC

Well I obviously never got around to this - patches always welcomed