From: Eli Zaretskii <eliz@gnu.org>
To: ilya@math.berkeley.edu
Cc: 19994@debbugs.gnu.org
Subject: bug#19994: 25.0.50; Unicode keyboard input on Windows
Date: Sat, 01 Aug 2015 10:40:05 +0300 [thread overview]
Message-ID: <83y4hvv4mi.fsf@gnu.org> (raw)
In-Reply-To: <83d1z8wuiz.fsf@gnu.org>
> Date: Fri, 31 Jul 2015 12:23:00 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 19994@debbugs.gnu.org
>
> Thanks. I committed this in your name, with a few minor stylistic
> changes, and also fixed a few typos in the comments. Sorry for a long
> delay in doing that.
>
> I also added a new variable, w32-use-fallback-wm-chars-method, which,
> when non-nil, makes Emacs use the old code from before your changes.
> This is meant to be a handy debugging aid, in case we discover some
> issues with the new code.
>
> Do you think there are any user-visible effects of your changes that
> are worthy of mentioning in NEWS? If so, please propose the text for
> NEWS.
>
> I leave it up to you to decide whether this bug should be closed, or
> if there's something else to be done about it.
Here's one problem evidently caused by the new code: invoke "emacs -Q"
and type "M-x" after it starts => you will see "x" being inserted into
*scratch*. This doesn't happen if w32-use-fallback-wm-chars-method is
non-nil.
This is a one-time problem: all the subsequent "M-x" are handled
correctly. It sounds like some initialization somewhere is missing?
Could you please look into that ASAP? TIA.
next prev parent reply other threads:[~2015-08-01 7:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 23:09 bug#19994: 25.0.50; Unicode keyboard input on Windows Ilya Zakharevich
2015-03-04 18:01 ` Eli Zaretskii
2015-03-06 0:43 ` Ilya Zakharevich
2015-03-06 10:52 ` Eli Zaretskii
2015-03-06 11:40 ` Ilya Zakharevich
2015-03-06 14:00 ` Eli Zaretskii
2015-07-01 10:07 ` Ilya Zakharevich
2015-07-09 0:02 ` Ilya Zakharevich
2015-07-31 9:23 ` Eli Zaretskii
2015-08-01 7:40 ` Eli Zaretskii [this message]
2015-08-02 14:42 ` Eli Zaretskii
2020-08-12 16:32 ` Stefan Kangas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y4hvv4mi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19994@debbugs.gnu.org \
--cc=ilya@math.berkeley.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.