From: Jason Rumney <jasonr@gnu.org>
To: Kenichi Handa <handa@ni.aist.go.jp>
Cc: lekktu@gmail.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: assertion failed: c == event->code
Date: Fri, 14 Dec 2007 08:47:48 +0000 [thread overview]
Message-ID: <47624334.109@gnu.org> (raw)
In-Reply-To: <E1J2z21-00055O-W3@etlken.m17n.org>
Kenichi Handa wrote:
> MULTIBYTE_CHAR_KEYSTROKE_EVENT should be for an Emacs's
> internal character code (i.e. emacs-mule encoded character
> in the trunk). Where in xterm.c, "a double byte character
> in the keyboard coding system" is generated?
>
Around line 6417, we have:
inev.ie.kind = (SINGLE_BYTE_CHAR_P (XFASTINT (c))
? ASCII_KEYSTROKE_EVENT
: MULTIBYTE_CHAR_KEYSTROKE_EVENT);
But I see c at that point is the result of a lookup in x-keysym-table,
so it might be OK.
next prev parent reply other threads:[~2007-12-14 8:47 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
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 [this message]
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=47624334.109@gnu.org \
--to=jasonr@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@ni.aist.go.jp \
--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).