From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 14403@debbugs.gnu.org
Subject: bug#14403: 24.3.50; [regression] Typing non-ascii characters on a non-GUI MS-Windows session
Date: Wed, 22 May 2013 17:22:15 -0400 [thread overview]
Message-ID: <jwv38teiufx.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <8338teu4ux.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 22 May 2013 23:39:02 +0300")
>> So a crude fix would be to check
>> "terminal->read_socket_hook == &tty_read_avail_input".
> Yes, crude.
>> What would be a good test to cleanly distinguish posix ttys from w32
>> "ttys"?
> How are they different?
posix ttys only emit bytes (aka encoded characters) in the event queue,
whereas according to this bug, w32 ttys emit characters (aka decoded
characters).
> And what about the Leim use case, which trips there as well?
While the Leim use case comes from the same commit, its source is
slightly different, so the two fixes are unrelated. I'm working on
a patch for that problem, but it doesn't fix this problem.
Stefan
next prev parent reply other threads:[~2013-05-22 21:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 19:11 bug#14403: 24.3.50; [regression] Typing non-ascii characters on a non-GUI MS-Windows session dmoncayo
2013-05-14 19:48 ` Eli Zaretskii
2013-05-14 22:28 ` Stefan Monnier
2013-05-15 8:13 ` Eli Zaretskii
2013-05-22 16:06 ` Stefan Monnier
2013-05-22 20:39 ` Eli Zaretskii
2013-05-22 21:22 ` Stefan Monnier [this message]
2013-05-23 2:46 ` Eli Zaretskii
2013-05-23 14:02 ` Stefan Monnier
2013-05-23 16:23 ` Eli Zaretskii
2013-05-23 17:22 ` Dani Moncayo
2013-05-23 17:38 ` Juanma Barranquero
2013-05-22 20:22 ` Juanma Barranquero
2013-05-22 20:34 ` Eli Zaretskii
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=jwv38teiufx.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=14403@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).