From: Eli Zaretskii <eliz@gnu.org>
To: "Alexander Prähauser" <ahprae@protonmail.com>,
"Po Lu" <luangruo@yahoo.com>
Cc: 68930@debbugs.gnu.org
Subject: bug#68930: 30.0.50; Emacs conflates C-Ω and C-ω
Date: Mon, 05 Feb 2024 21:10:02 +0200 [thread overview]
Message-ID: <86eddq20dx.fsf@gnu.org> (raw)
In-Reply-To: <878r3yalww.fsf@protonmail.com> (message from Alexander Prähauser on Mon, 05 Feb 2024 16:58:02 +0000)
[Please use Reply All to reply, to keep the bug tracker CC'ed.]
> Date: Mon, 05 Feb 2024 16:58:02 +0000
> From: Alexander Prähauser <ahprae@protonmail.com>
>
> "Eli Zaretskii" <eliz@gnu.org> writes:
>
> >> Date: Sun, 04 Feb 2024 20:49:26 +0000
> >> From: Alexander Prähauser via "Bug reports for GNU Emacs,
> >> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> >>
> >>
> >> Emacs confuses C-ω and C-Ω. This seems to happen regardless of the init file.
> >> For instance, if started with a basic init containing only the lines
> >>
> >> (define-key global-map (kbd "C-ω") 'kill-region)
> >> (define-key global-map (kbd "C-Ω") 'copy-to-register)
> >>
> >> the commands are recalled by exactly the reversed key combinations, C-Ω
> >> kills and C-ω copies to register. Both Ω and ω are here in the xkb-map
> >> of the keyboard layout as unicode characters, U03A9 and U03C9
> >> respectively. I tried using C-Ω and C-ω as key combinations for commands
> >> in the Firefox-plugin Tridactyl to see if it confuses them as well, but
> >> it seems to be able to distinguish them.
> >
> > What does "C-h l" say about what keys Emacs received?
>
> It also lists them the wrong way around, so if I type C-ω it lists C-Ω
> and vice versa.
So are you sure nothing is wrong with your keyboard setup?
Adding Po Lu in case he has some ideas or comments.
next prev parent reply other threads:[~2024-02-05 19:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 20:49 bug#68930: 30.0.50; Emacs conflates C-Ω and C-ω Alexander Prähauser via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-05 12:48 ` Eli Zaretskii
[not found] ` <878r3yalww.fsf@protonmail.com>
2024-02-05 19:10 ` Eli Zaretskii [this message]
2024-02-05 23:00 ` Alexander Prähauser via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-06 0:07 ` Alexander Prähauser via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-06 4:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-06 12:33 ` Eli Zaretskii
2024-02-06 12:57 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-06 13:11 ` Alexander Prähauser via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-06 13:22 ` Alexander Prähauser via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-06 14:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-06 12:34 ` Alexander Prähauser via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87r0hp9d4x.fsf@protonmail.com>
[not found] ` <87o7cs6a1x.fsf@yahoo.com>
[not found] ` <87eddoa3mp.fsf@protonmail.com>
[not found] ` <87jzng5uz1.fsf@yahoo.com>
[not found] ` <87a5oca09q.fsf@protonmail.com>
[not found] ` <878r3w5r56.fsf@yahoo.com>
[not found] ` <875xyz9or5.fsf@protonmail.com>
[not found] ` <87wmrf2ndz.fsf@yahoo.com>
[not found] ` <871q9n9n1f.fsf@protonmail.com>
2024-02-08 12:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-08 13:00 ` Alexander Prähauser via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-08 13:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-08 14:32 ` Alexander Prähauser via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-24 9:33 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86eddq20dx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=68930@debbugs.gnu.org \
--cc=ahprae@protonmail.com \
--cc=luangruo@yahoo.com \
/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.