From: Gregory Heytings <gregory@heytings.org>
To: Marcin Kasperski <Marcin.Kasperski@mekk.waw.pl>
Cc: Po Lu <luangruo@yahoo.com>, 60711@debbugs.gnu.org
Subject: bug#60711: Compose fails to generate ≤ and ≥ (only those two! and only in emacs!)
Date: Wed, 11 Jan 2023 20:59:09 +0000 [thread overview]
Message-ID: <502d6ee86a4d9b248aed@heytings.org> (raw)
In-Reply-To: <CAJQm8RZNitx928L6n1Qqe_BndAgXJF3P2hkbPY=hT4QA1dxO6w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
>> What's that "floating window" you mention?
>
> Attached as floating-window.png (this is what I see after Compose >)
>
That doesn't seem to be an Emacs thing. Do you see the same floating
window with other apps? Do you by chance know the name of the app that
displays that floating window?
>> What does Emacs tell you when you type "C-h k Compose _ >"?
>
> Nothing. It still waits displaying prompt „Describe the following key…"
> Same for Compose >= etc.
>
> But when I enter Compose -> (which work) it displays info about
> self-insert-command
>
>> And also what does "C-h l" show _after_ you type those?
>
> …
> <return> ;; newline
> C-h l ;; view-lossage
>
> (I typed this sequence after pressing return)
>
As Eli just said, it means that Emacs didn't receive any character.
next prev parent reply other threads:[~2023-01-11 20:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 15:13 bug#60711: Compose fails to generate ≤ and ≥ (only those two! and only in emacs!) Marcin Kasperski
2023-01-10 15:15 ` Marcin Kasperski
2023-01-10 16:01 ` Gregory Heytings
2023-01-10 17:07 ` Eli Zaretskii
2023-01-11 7:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-11 8:45 ` Gregory Heytings
2023-01-11 10:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-11 18:45 ` Marcin Kasperski
2023-01-11 18:49 ` Marcin Kasperski
2023-01-11 18:54 ` Marcin Kasperski
2023-01-11 19:18 ` Marcin Kasperski
2023-01-11 21:15 ` Gregory Heytings
2023-01-11 23:05 ` Andreas Schwab
2023-01-13 14:26 ` Marcin Kasperski
2023-01-13 14:41 ` Marcin Kasperski
2023-01-15 0:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-14 21:54 ` Gregory Heytings
2023-01-11 21:11 ` Gregory Heytings
2023-01-11 20:01 ` Eli Zaretskii
2023-01-11 20:59 ` Gregory Heytings [this message]
2023-01-11 21:02 ` Gregory Heytings
2023-01-12 1:25 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-16 9:41 ` Gregory Heytings
2023-01-16 9:57 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-16 12:31 ` Gregory Heytings
2023-01-17 0:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-09 11:01 ` Gregory Heytings
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=502d6ee86a4d9b248aed@heytings.org \
--to=gregory@heytings.org \
--cc=60711@debbugs.gnu.org \
--cc=Marcin.Kasperski@mekk.waw.pl \
--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.