From: Tomas Nordin <tomasn@posteo.net>
To: Stefan Kangas <stefan@marxist.se>, Eli Zaretskii <eliz@gnu.org>
Cc: 30043@debbugs.gnu.org
Subject: bug#30043: 25.3; C-M-e inserts euro character
Date: Sun, 29 Sep 2019 15:20:10 +0200 [thread overview]
Message-ID: <87k19r1bp1.fsf@fliptop.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <CADwFkmkpUaCL9RVvMgxX+anX9kuacHBY3=1--UD_R+vebCkWdA@mail.gmail.com>
Stefan Kangas <stefan@marxist.se> writes:
> tags 30043 + notabug
> close 30043
> quit
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: Tomas Nordin <tomasn@posteo.net>
>>> Cc: 30043@debbugs.gnu.org
>>> Date: Sat, 13 Jan 2018 23:10:43 +0100
>>>
>>> > Does it help to set w32-use-fallback-wm-chars-method to a non -nil
>>> > value in Emacs 25.3?
>>>
>>> Yes, that removes the problem.
>>
>> So I guess you somehow have a keyboard which doesn't fit the new
>> keyboard input code introduced by Emacs 25, and need to use this
>> fallback variable to avoid the problem.
>
> I believe that was the correct answer, and nothing of the rest of the
> discussion indicated otherwise. I'm therefore closing this as notabug.
It seems to me then that the correct answer is that keyboards with
swedish layout on Windows does not fit the new keyboard input code. I
see the same on a laptop now with emacs 26.2. It is strange that no-one
else in this country complains.
Using the work-around with setting w32-use-fallback-wm-chars-method
solves the problem. But the docstring of that variable suggests that I
shouldn't have to use it unless debugging something.
I am not going to argue with the closing but I don't think this is
specific to one specific keyboard. It was reproduced on several
keyboards on different machines.
Thanks
--
Tomas
next prev parent reply other threads:[~2019-09-29 13:20 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 15:11 bug#30043: 25.3; C-M-e inserts euro character tomasn
2018-01-09 18:33 ` Eli Zaretskii
2018-01-09 21:06 ` Tomas Nordin
2018-01-10 3:32 ` Eli Zaretskii
2018-01-10 21:49 ` Tomas Nordin
2018-01-11 15:55 ` Eli Zaretskii
2018-01-13 22:10 ` Tomas Nordin
2018-01-14 3:34 ` Eli Zaretskii
2018-01-14 19:01 ` Tomas Nordin
2018-01-14 19:57 ` Eli Zaretskii
2018-01-14 20:22 ` Tomas Nordin
2018-01-15 5:15 ` Eli Zaretskii
2018-01-18 10:59 ` Tomas Nordin
2018-01-18 11:16 ` Tomas Nordin
2019-09-28 23:03 ` Stefan Kangas
2019-09-29 13:20 ` Tomas Nordin [this message]
2019-09-29 15:42 ` Stefan Kangas
2019-09-29 15:45 ` Stefan Kangas
2019-09-29 15:52 ` Eli Zaretskii
2019-09-29 16:00 ` Eli Zaretskii
2019-09-29 16:08 ` Eli Zaretskii
2019-09-29 16:19 ` Eli Zaretskii
2019-09-29 16:27 ` Eli Zaretskii
2019-09-29 18:32 ` Tomas Nordin
2019-09-29 16:08 ` Stefan Kangas
2019-09-29 18:21 ` Tomas Nordin
2019-10-13 10:00 ` Tomas Nordin
2019-10-13 10:33 ` Eli Zaretskii
2019-10-13 19:07 ` Tomas Nordin
2019-10-13 20:48 ` Eli Zaretskii
2022-04-26 13:59 ` Lars Ingebrigtsen
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=87k19r1bp1.fsf@fliptop.i-did-not-set--mail-host-address--so-tickle-me \
--to=tomasn@posteo.net \
--cc=30043@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stefan@marxist.se \
/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).