Timeline for Key bound to string does not handle some chars in string correctly
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 14, 2016 at 17:32 | comment | added | Stefan | @T.Verron: The existing string representation of a sequence of events can't be changed without breaking existing code, so we can't just call kbd for the user, because we can't know if the string uses the old format or the "kdb format". My favorite option would be to signal an error when using a string as a "sequence of events" (or at least emit a warning) so as to force authors to update their code and use a vector (which they can do via kbd if they want). | |
| Oct 14, 2016 at 17:28 | comment | added | Stefan | Right, I guess 8th is a better way to describe it (I was thinking "bit 7" when counting from 0, but I wouldn't call bit 0 "the 0th bit", I'd call it "the first bit"). | |
| Oct 14, 2016 at 16:33 | comment | added | T. Verron | Also, I think you mean that 128 is the 8th* bit. | |
| Oct 14, 2016 at 16:31 | vote | accept | T. Verron | ||
| Oct 14, 2016 at 16:31 | comment | added | T. Verron | Thanks for the detailed explanation. Out of curiosity, I went to check the release date for emacs 19... apparently that's 1994 (first beta in 1992). It's not that often that I meet a bug that's almost as old as I am! :) One question though: it seems from what you say that kbd does basically the same job as this legacy code (converting a string to a sequence of events), but much better from a 2016 point of view. Wouldn't this behavior be "easily" fixed by replacing this legacy code with calls to kbd where applicable (e.g. when binding keys)? | |
| Oct 14, 2016 at 16:21 | history | answered | Stefan | CC BY-SA 3.0 |