From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 12055@debbugs.gnu.org
Subject: bug#12055: 24.1.50; Characters "á" and "é" are not correctly displayed on a Windows terminal
Date: Sat, 28 Jul 2012 01:45:42 +0200 [thread overview]
Message-ID: <CAAeL0ST3Kx0jAORZ6k6BKntAPoi3oH1STjNTUoevbvRZiZaqMg@mail.gmail.com> (raw)
In-Reply-To: <83zk6li6gd.fsf@gnu.org>
On Fri, Jul 27, 2012 at 5:12 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> There are 2 messages for each keystroke:
Not exactly, see below.
> one when the key is pressed, the other when it is released. Please
> post here the exact output, and please tell for each pair of such
> messages which character did you type.
Dead key '
warning: key_event: 1 1 0xde 0x28 {0x0 0x0} 0x0
warning: key_event: 0 1 0xde 0x0 {0xffffffef 0xef} 0x0
warning: key_event: 0 1 0xde 0x28 {0xffffffef 0xef} 0x0
a
warning: key_event: 1 1 0x41 0x1e {0xffffffa0 0xa0} 0x0
warning: key_event: 0 1 0x41 0x1e {0x61 0x61} 0x0
Dead key '
warning: key_event: 1 1 0xde 0x28 {0x0 0x0} 0x0
warning: key_event: 0 1 0xde 0x0 {0xffffffef 0xef} 0x0
warning: key_event: 0 1 0xde 0x28 {0xffffffef 0xef} 0x0
e
warning: key_event: 1 1 0x45 0x12 {0xffffff82 0x82} 0x0
warning: key_event: 0 1 0x45 0x12 {0x65 0x65} 0x0
etc.
Juanma
next prev parent reply other threads:[~2012-07-27 23:45 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 12:13 bug#12055: 24.1.50; Characters "á" and "é" are not correctly displayed on a Windows terminal Dani Moncayo
2012-07-26 16:13 ` Eli Zaretskii
2012-07-26 16:24 ` Juanma Barranquero
2012-07-26 16:42 ` bug#12055: " Eli Zaretskii
2012-07-26 16:49 ` Juanma Barranquero
2012-07-26 17:18 ` bug#12055: " Eli Zaretskii
2012-07-26 18:09 ` Eli Zaretskii
2012-07-26 18:42 ` Juanma Barranquero
2012-07-26 18:29 ` Juanma Barranquero
2012-07-26 20:03 ` bug#12055: " Eli Zaretskii
2012-07-26 22:40 ` Dani Moncayo
2012-07-27 6:45 ` bug#12055: " Eli Zaretskii
2012-07-27 8:35 ` Dani Moncayo
2012-07-27 9:04 ` bug#12055: " Eli Zaretskii
2012-07-27 15:12 ` Eli Zaretskii
2012-07-27 16:46 ` Jason Rumney
2012-07-27 18:03 ` Eli Zaretskii
2012-07-27 18:22 ` Eli Zaretskii
2012-07-27 23:45 ` Juanma Barranquero [this message]
2012-07-28 1:12 ` Dani Moncayo
2012-07-28 8:04 ` bug#12055: " Eli Zaretskii
2012-07-28 10:06 ` Eli Zaretskii
2012-07-28 11:55 ` Dani Moncayo
2012-07-28 12:23 ` bug#12055: " Eli Zaretskii
2012-07-28 12:49 ` Dani Moncayo
2012-07-28 15:02 ` bug#12055: " Eli Zaretskii
2012-07-28 12:30 ` bug#12055: " Eli Zaretskii
2012-07-28 13:57 ` Dani Moncayo
2012-07-28 16:07 ` Juanma Barranquero
2012-07-28 16:12 ` Dani Moncayo
2012-07-28 16:11 ` Juanma Barranquero
2012-07-28 16:44 ` bug#12055: " Eli Zaretskii
2012-07-28 17:01 ` Eli Zaretskii
2012-07-26 16:44 ` Dani Moncayo
2012-07-28 14:12 ` Dani Moncayo
2012-07-28 15:01 ` bug#12055: " Eli Zaretskii
2012-07-28 15:23 ` Dani Moncayo
2012-07-28 15:34 ` Dani Moncayo
2012-07-28 16:27 ` bug#12055: " Eli Zaretskii
2012-07-28 15:35 ` Eli Zaretskii
2012-07-28 15:46 ` Dani Moncayo
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=CAAeL0ST3Kx0jAORZ6k6BKntAPoi3oH1STjNTUoevbvRZiZaqMg@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=12055@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).