From: Robert Pluim <rpluim@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: 54562@debbugs.gnu.org
Subject: bug#54562: 28.0.91; Emoji sequence not composed
Date: Fri, 25 Mar 2022 15:14:40 +0100 [thread overview]
Message-ID: <87a6deunjj.fsf@gmail.com> (raw)
In-Reply-To: <87sfr66sb7.fsf@yahoo.com> (Po Lu's message of "Fri, 25 Mar 2022 22:05:32 +0800")
>>>>> On Fri, 25 Mar 2022 22:05:32 +0800, Po Lu <luangruo@yahoo.com> said:
Po> Eli Zaretskii <eliz@gnu.org> writes:
>> Why do you think what they do is "correct"? AFAIK, we use the Unicode
>> Standard's definition of Emoji sequences to decide when U+FE0F
>> warrants an Emoji representation. maybe those other applications
>> default to Emoji representation of every character that can possibly
>> have such a representation, but in Emacs such a default cannot make
>> sense.
Po> I don't know whether or not their behavior is correct, but this sequence
Po> is seen in the wild (for example, the Mac OS input methods generate
Po> these sequences), so maybe it is worth supporting.
Iʼve just tested adding U+20E3 to
`auto-composition-emoji-eligible-codepoints', and it seems to work OK.
Robert
--
next prev parent reply other threads:[~2022-03-25 14:14 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87bkxu8k7t.fsf.ref@yahoo.com>
2022-03-25 9:17 ` bug#54562: 28.0.91; Emoji sequence not composed Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-25 10:27 ` Eli Zaretskii
2022-03-25 10:32 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-25 10:54 ` Robert Pluim
2022-03-25 11:47 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-25 12:15 ` Eli Zaretskii
2022-03-25 12:46 ` Andreas Schwab
2022-03-25 13:05 ` Eli Zaretskii
2022-03-25 13:14 ` Andreas Schwab
2022-03-25 13:30 ` Robert Pluim
2022-03-25 13:57 ` Andreas Schwab
2022-03-25 13:44 ` Eli Zaretskii
2022-03-25 14:03 ` Andreas Schwab
2022-03-25 14:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-25 14:14 ` Robert Pluim [this message]
2022-03-26 1:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-26 5:56 ` Eli Zaretskii
2022-03-26 16:51 ` Lars Ingebrigtsen
2022-03-27 0:32 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-27 15:10 ` Robert Pluim
2022-03-28 0:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-28 7:47 ` Robert Pluim
2022-03-28 11:51 ` Eli Zaretskii
2022-03-28 12:46 ` Robert Pluim
2022-03-28 13:12 ` Eli Zaretskii
2022-03-28 14:59 ` Robert Pluim
2022-03-28 16:07 ` Eli Zaretskii
2022-03-29 10:45 ` Robert Pluim
2022-03-29 11:44 ` Eli Zaretskii
2022-03-29 14:50 ` Robert Pluim
2022-03-29 15:42 ` Eli Zaretskii
2022-03-29 15:59 ` Robert Pluim
2022-03-29 16:49 ` Eli Zaretskii
2022-03-28 13:19 ` Andreas Schwab
2022-03-28 15:01 ` Robert Pluim
2022-03-28 15:35 ` Andreas Schwab
2022-03-28 16:11 ` Eli Zaretskii
2022-03-28 16:20 ` Andreas Schwab
2022-03-28 16:26 ` Robert Pluim
2022-03-28 16:41 ` Andreas Schwab
2022-03-28 17:10 ` Eli Zaretskii
2022-03-28 17:14 ` Eli Zaretskii
2022-03-28 17:39 ` Andreas Schwab
2022-03-28 18:12 ` Eli Zaretskii
2022-03-28 18:14 ` Andreas Schwab
2022-03-28 18:15 ` Eli Zaretskii
2022-03-25 11:23 ` 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
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=87a6deunjj.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=54562@debbugs.gnu.org \
--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 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).