unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Fernando de Morais <fernandodemorais.jf@gmail.com>
To: 57066@debbugs.gnu.org
Cc: Protesilaos Stavrou <info@protesilaos.com>
Subject: bug#57066: 29.0.50; Complex emoji overlaps with text
Date: Tue, 09 Aug 2022 08:23:32 -0300	[thread overview]
Message-ID: <87zggdek3v.fsf@gmail.com> (raw)
In-Reply-To: <87r11pzsgb.fsf@protesilaos.com> (Protesilaos Stavrou's message of "Tue, 09 Aug 2022 12:17:40 +0300")

[-- Attachment #1: Type: text/plain, Size: 643 bytes --]

Hello,

I've been experiencing the same issue on Emacs 28.1[1] since upgrading
HarfBuzz to 5.1.0 (with the previous version, 5.0.1, composed sequences
were not displayed properly, as reported in bug#56789[2]).

I couldn't reproduce exactly the same steps listed, because the command
C-x 8 e s is not available, but follows attached a screenshot to
illustrate the same problem faced by Protesilaos.

Thanks.

Footnotes:
[1] GNU Emacs 28.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.33,
     cairo version 1.17.6) of 2022-04-27

[2]  https://mail.gnu.org/archive/html/bug-gnu-emacs/2022-07/msg02241.html

-- 
Regards,
Fernando de Morais.


[-- Attachment #2: Print. --]
[-- Type: image/png, Size: 268323 bytes --]

  parent reply	other threads:[~2022-08-09 11:23 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09  9:17 bug#57066: 29.0.50; Complex emoji overlaps with text Protesilaos Stavrou
2022-08-09 11:14 ` Eli Zaretskii
2022-08-09 11:28   ` Protesilaos Stavrou
2022-08-09 12:01     ` Eli Zaretskii
2022-08-09 12:50       ` Protesilaos Stavrou
2022-08-09 16:05         ` Eli Zaretskii
2022-08-09 17:17           ` Protesilaos Stavrou
2022-08-09 17:31             ` Eli Zaretskii
2022-08-09 17:41               ` Protesilaos Stavrou
2022-08-09 17:54                 ` Eli Zaretskii
2022-08-10  3:15                   ` Protesilaos Stavrou
2022-08-10 12:33                     ` Eli Zaretskii
2022-08-11  4:07                       ` Protesilaos Stavrou
2022-08-11  6:01                         ` YAMAMOTO Mitsuharu
2022-08-11  6:24                           ` YAMAMOTO Mitsuharu
2022-08-11  6:35                             ` Protesilaos Stavrou
2022-08-11  6:49                             ` Eli Zaretskii
2022-08-11  7:23                               ` YAMAMOTO Mitsuharu
2022-08-11  7:43                                 ` Eli Zaretskii
2022-08-11  8:57                                   ` YAMAMOTO Mitsuharu
2022-08-11  9:35                                     ` Eli Zaretskii
2022-08-11  9:49                                       ` YAMAMOTO Mitsuharu
2022-08-09 11:23 ` Fernando de Morais [this message]
2022-08-09 11:54   ` Eli Zaretskii
2022-08-09 12:06     ` Fernando de Morais
2022-08-09 18:28   ` Lars Ingebrigtsen
2022-08-10  3:16     ` Protesilaos Stavrou

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=87zggdek3v.fsf@gmail.com \
    --to=fernandodemorais.jf@gmail.com \
    --cc=57066@debbugs.gnu.org \
    --cc=info@protesilaos.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).