[Konsole-devel] [Bug 306982] New: Mismanagement of keys for suspending output

[Ganton]

https://bugs.kde.org/show_bug.cgi?id=306982

            Bug ID: 306982
          Severity: normal
           Version: 2.8.4
          Priority: NOR
          Assignee: konsole-devel at kde.org
           Summary: Mismanagement of keys for suspending output
    Classification: Unclassified
                OS: Linux
          Reporter: kubry at terra.com
          Hardware: Ubuntu Packages
            Status: UNCONFIRMED
         Component: monitoring
           Product: konsole

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 [...]"

-- 
You are receiving this mail because:
You are the assignee for the bug.