From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: simon@polaris64.net, 51659@debbugs.gnu.org
Subject: bug#51659: 29.0.50; emoji.el: incorrect description for some emojis in emoji-list
Date: Sun, 07 Nov 2021 17:16:12 +0200 [thread overview]
Message-ID: <83ee7s808z.fsf@gnu.org> (raw)
In-Reply-To: <87wnlkggy3.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun, 07 Nov 2021 15:48:20 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 51659@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
> Date: Sun, 07 Nov 2021 15:48:20 +0100
>
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
> > Perhaps emoji.el is mis-parsing the emoji file... I'll try to debug.
>
> No, there's something weird going on in `find-composition' here? Eli,
> could you have a look -- it's a bit mysterious.
>
> (insert "\x263A\xFE0Flalalalalal")
> => ☺️lalalalalal
>
> (find-composition (point)) on both of those return the composition on
> the first cluster.
What are "both of those"? And what do you mean by the "first
cluster"?
> Now, the doc string says:
>
> ---
> If there’s no composition at POS, and the optional 2nd argument LIMIT
> is non-nil, search for a composition toward the position given by LIMIT.
> ---
>
> So I interpret a nil value shouldn't search?
It shouldn't search if POS is not included in any composition, no.
> (find-composition (point) (point)) returns absolutely the same as a nil
> value on the "lala" bits.
That's expected.
But I still don't understand what is the problem. What did you try to
accomplish, and what happened instead?
next prev parent reply other threads:[~2021-11-07 15:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-07 12:45 bug#51659: 29.0.50; emoji.el: incorrect description for some emojis in emoji-list Simon Pugnet
2021-11-07 14:29 ` Lars Ingebrigtsen
2021-11-07 14:48 ` Lars Ingebrigtsen
2021-11-07 15:00 ` Lars Ingebrigtsen
2021-11-07 15:02 ` Lars Ingebrigtsen
2021-11-07 15:16 ` Eli Zaretskii
2021-11-07 15:20 ` Lars Ingebrigtsen
2021-11-07 15:30 ` Eli Zaretskii
2021-11-07 15:39 ` Lars Ingebrigtsen
2021-11-07 15:16 ` Eli Zaretskii [this message]
2021-11-07 15:19 ` 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=83ee7s808z.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51659@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=simon@polaris64.net \
/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).