From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Cc: 59306@debbugs.gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#59306: 29.0.50; Resurrected bug?
Date: Fri, 25 Nov 2022 17:11:50 +0800 [thread overview]
Message-ID: <87sfi7xusp.fsf@yahoo.com> (raw)
In-Reply-To: <CAO48Bk-ToNCxsNBwPnSmQfdGXz8LpdhbK3s3DYh7_zAx3kLq6w@mail.gmail.com> (Pedro Andres Aranda Gutierrez's message of "Fri, 25 Nov 2022 09:28:01 +0100")
Pedro Andres Aranda Gutierrez <paaguti@gmail.com> writes:
> It definitely looks like that, because it doesn't happen on my macOS
> Emacs (compiled from the same git as for Linux). When I return home, I
> was thinking about compiling Emacs on Linuux for GTK3 but disabling
> CAIRO... would that make eny sense?
Yes, that would eliminate the bug.
next prev parent reply other threads:[~2022-11-25 9:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 11:49 bug#59306: 29.0.50; Resurrected bug? Pedro Andres Aranda Gutierrez
2022-11-16 13:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-17 1:28 ` Dmitry Gutov
2022-11-17 2:10 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-19 6:03 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-19 9:08 ` Pedro Andres Aranda Gutierrez
2022-11-19 10:03 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-19 14:06 ` Dmitry Gutov
2022-11-20 0:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-20 16:47 ` Dmitry Gutov
2022-11-21 0:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-25 8:28 ` Pedro Andres Aranda Gutierrez
2022-11-25 9:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-11-25 16:09 ` Pedro Andres Aranda Gutierrez
2022-11-17 6:22 ` Pedro Andres Aranda Gutierrez
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=87sfi7xusp.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=59306@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=luangruo@yahoo.com \
--cc=paaguti@gmail.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).