unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tomas Nordin <tomasn@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 30043@debbugs.gnu.org
Subject: bug#30043: 25.3; C-M-e inserts euro character
Date: Sun, 14 Jan 2018 21:22:39 +0100	[thread overview]
Message-ID: <878td02nsg.fsf@fliptop.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <83po6cz005.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Tomas Nordin <tomasn@posteo.net>
>> Cc: 30043@debbugs.gnu.org
>> Date: Sun, 14 Jan 2018 20:01:14 +0100
>> 
>> > 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.
>> 
>> Does it mean that the new input code has no fault but the keyboard
>> probably has a problem?
>
> I don't think this is a problem, I think this is how your keyboard is
> supposed to work.  But since you don't like it, I mentioned the
> variable which can be used to get back the old Emacs 24 behavior, if
> that's what you want.

Yes, I do prefer to be able to call end-of-defun by a familiar
key-binding. If I test this on some other stations with other keyboards
with the same result, will that yield the same recommendation with
setting the fall-back variable?





  reply	other threads:[~2018-01-14 20:22 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 [this message]
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
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=878td02nsg.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 \
    /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).