Re: Coredumping bug in 21 (read-kbd-macro)

Hrvoje> Yup. "\H-a" is equivalent to "H-a", which gets processed correctly by Hrvoje> `read-kbd-macro'. Hrvoje> Nothing, as far as I can tell. ?\H-a evaluates to ?a. The code is Hrvoje> *supposed* to produce some weird constants, to make some sense out of Hrvoje> FSF bytecode. In XEmacs 19 it worked because characters were integers Hrvoje> (someone should check what ?\H-a evaluates to in XEmacs 19). In Hrvoje> XEmacs 20/no-mule these "big" chars get trimmed to a byte and we don't Hrvoje> notice the ebolification. In XEmacs 20/Mule the "big" chars get Hrvoje> turned into illegal Emchars and we get a crash. If you read the Cltl2 chapter on characters, you can see that the FSF model is actually consistent with the Common Lisp model (which in turn was designed to support Emacs-like editors). http://fas.sfu.ca/1/projects/ElectronicLibrary/Collections/CMPT///cs-book... However, even Cltl2 admits that the idea of bucky bits being properties of characters was a dismal failure. Separating the concepts of characters and keystrokes is the Right Thing. Martin