From: Manuel Giraud via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Po Lu <luangruo@yahoo.com>, 65432-done@debbugs.gnu.org
Subject: bug#65432: 30.0.50; jerky image movements when zoomed
Date: Sun, 03 Sep 2023 15:41:52 +0200 [thread overview]
Message-ID: <87y1hnbcgv.fsf@ledu-giraud.fr> (raw)
In-Reply-To: <83fs3v94hb.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 03 Sep 2023 09:05:04 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Po Lu <luangruo@yahoo.com>
>> Cc: 65432@debbugs.gnu.org, manuel@ledu-giraud.fr
>> Date: Sat, 02 Sep 2023 15:35:05 +0800
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > Ping! Should we mention this issue in PROBLEMS?
>>
>> I think so. I will write an entry.
>
> I see you've written it on the emacs-29 branch, so I'm now closing
> this bug.
Ok. I'm currently using "--without-cairo" to fix this issue. FTR, Po,
what is the drawback of not using cairo in Emacs? Thanks.
--
Manuel Giraud
next prev parent reply other threads:[~2023-09-03 13:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 14:45 bug#65432: 30.0.50; jerky image movements when zoomed Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-21 19:10 ` Eli Zaretskii
2023-08-22 2:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-24 13:48 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-24 14:41 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-26 7:58 ` Eli Zaretskii
2023-09-02 7:31 ` Eli Zaretskii
2023-09-02 7:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-03 6:05 ` Eli Zaretskii
2023-09-03 13:41 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-09-03 13:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87y1hnbcgv.fsf@ledu-giraud.fr \
--to=bug-gnu-emacs@gnu.org \
--cc=65432-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=manuel@ledu-giraud.fr \
/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.