> On Wed, Jan 11, 2012 at 07:00:52PM +0100, Axel Beckert wrote:
> I reported it to the GNU Screen developers at
> https://savannah.gnu.org/bugs/index.php?35287
I did some more thinking on this and I think I have a conclusion.
First, my initial report was wrong --- typing fast does not trigger the
default action --- it triggers the control-key action for the second
key, e.g. ^A-space yields ^A-control(space), which also happens to be
^@, or the null byte. This probably happens because the control was
down for the ^A, and might pass into the next key.
Second, I notice that they map control(space) to the same action as
space in the default bindings (which were not modified by Debian):
ktab[' '].nr = ktab[Ctrl(' ')].nr =
---------
ktab['n'].nr = ktab[Ctrl('n')].nr = RC_NEXT;
Third, because the control-space (^@) is coming from the read() kernel
call (and I don't see them remapping 'read' to their own function), I
realized the problem might not be with screen but perhaps the terminal
driver. However, I tried to reproduce the problem from the command line
by typing ^A-space quickly and did not see that behavior.
I then started to wonder why I had not see this behavior with screen on
my previous BSD system so I booted it up, and found it has exactly the
fix I just discovered, e.g. binding ^@ to the same action as space.
So, I think I have a solution for my problem, and that is to map
control-key to the same action as the non-control key. I see them doing
that in several default screen bindings, and I will just follow that if
I see another key exhibiting this problem.
So, for me, I don't need to peruse this issue further, but am available
if someone else needs help on this. Thanks for looking into this for me.
--
Bruce Momjian <br...@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
