[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: read-key-sequence(-vector) on Shift left/right gives[left]/[right],

From: Drew Adams
Subject: RE: read-key-sequence(-vector) on Shift left/right gives[left]/[right], not [S-left]/[S-right] ?
Date: Tue, 7 Sep 2004 08:47:07 -0700

From: Stefan

> > Shouldn't code be able to read user input
> > without paying attention to key bindings?

> When do you stop?  After one key, two keys, three?

Point taken.

What I really meant was wrt dropping the Shift modifier. Read-key-* has no
trouble knowing to stop after one key, if that key is undefined. For
example, if C-M-+ is undefined, it returns this: [-67108821]; it doesn't ask
itself when to stop.

Otherwise (a key sequence is defined), it continues to read until it gets
the complete key sequence. I would expect it to have such behavior all the
time, and not make an exception of Shift. That's all.


 - read-key-* should not drop the Shift modifier: if Shift-* is undefined
and * is defined, it should act as it does with any other undefined key
sequence (return Shift-*), instead of returning *
 - if read-key-* does drop the Shift modifier, then this should be
 - read-key-* should in any case optionally be able to not drop the Shift


reply via email to

[Prev in Thread] Current Thread [Next in Thread]