From: Jason Rumney <jasonr@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
Emacs-Devel <emacs-devel@gnu.org>
Subject: Re: assertion failed: c == event->code
Date: Thu, 13 Dec 2007 14:16:35 +0000 [thread overview]
Message-ID: <47613EC3.7020004@gnu.org> (raw)
In-Reply-To: <f7ccd24b0712121000l79505381wc71bec5334f4d025@mail.gmail.com>
Juanma Barranquero wrote:
> On Dec 12, 2007 6:30 PM, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>
>
>> Hmm.. if you just remove this eassert, you should get back the previous
>> behavior. But then I wonder: is this previous behavior correct, and if
>> so, why?
>>
>
> No idea.
>
>
>> Basically, the issue is that when a key is pressed, the W32 code inserts
>> a "ASCII_KEYSTROKE_EVENT" in the queue, even for non-ASCII chars, and
>> then keyboard.c applies a "& 0377" to it, so there's a risk of losing
>> some bits and turning a non-ASCII keypress into some ASCII char.
>>
>
> Without the eassert, C-ñ returns ' (U+2018, translated from \221), C-ç
> returns ‡ (U+2021, translated from \207). Not sure whether that is
> intended or not.
>
What is your locale set to, and keyboard-coding-system?
Also, does this happen with emacs -Q?
Since Windows effectively blocks Cntl and AltGr being used together, the
only sequences I can type are C-£ and C-¬, both of which work correctly
with a UK English Windows locale, and keyboard-coding-system set to cp1252.
Looking at the actual code for ASCII_KEYSTROKE_EVENT, it really means
UNIBYTE_CHAR_KEYSTROKE_EVENT, as the mask is against \0377 (0xff), and a
test in xterm.c tests for SINGLE_BYTE_CHAR_P.
Other naming in that enum is not clear, as NONASCII_KEYSTROKE_EVENT
actually means FUNCTION_KEYSTROKE_EVENT, or NON_CHAR_KEYSTROKE_EVENT.
MULTIBYTE_CHAR_KEYSTROKE_EVENT seems clearer, but it is not clear from
the comments, nor the code in xterm.c, whether it should be an
emacs-mule encoded character, or a double byte character in the keyboard
coding system, as the code in xterm.c seems to generate both.
next prev parent reply other threads:[~2007-12-13 14:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 15:14 assertion failed: c == event->code Juanma Barranquero
2007-12-12 17:30 ` Stefan Monnier
2007-12-12 18:00 ` Juanma Barranquero
2007-12-12 20:05 ` Stefan Monnier
2007-12-12 22:54 ` Juanma Barranquero
2007-12-12 23:41 ` Jason Rumney
2007-12-13 14:16 ` Jason Rumney [this message]
2007-12-13 15:09 ` Juanma Barranquero
2007-12-13 16:37 ` Jason Rumney
2007-12-13 16:44 ` Juanma Barranquero
2007-12-14 9:24 ` Jason Rumney
2007-12-14 10:11 ` Juanma Barranquero
2007-12-14 1:08 ` Kenichi Handa
2007-12-14 8:47 ` Jason Rumney
2007-12-14 11:11 ` Kenichi Handa
2007-12-14 12:23 ` Jason Rumney
2007-12-14 14:25 ` Juanma Barranquero
2007-12-16 15:19 ` Juanma Barranquero
2007-12-16 20:49 ` Jason Rumney
2007-12-16 20:53 ` Juanma Barranquero
2007-12-16 20:59 ` Juanma Barranquero
2007-12-16 21:25 ` Miles Bader
2007-12-17 1:52 ` Jason Rumney
2007-12-17 9:06 ` Juanma Barranquero
2007-12-12 18:36 ` Andreas Schwab
2007-12-12 17:54 ` martin rudalics
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47613EC3.7020004@gnu.org \
--to=jasonr@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).