From: Po Lu 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: 30088@debbugs.gnu.org, npostavs@users.sourceforge.net,
damien@cassou.me, dgutov@yandex.ru, charles@aurox.ch,
Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#30088: Rendering glitch with double buffering enabled
Date: Tue, 22 Feb 2022 09:05:35 +0800 [thread overview]
Message-ID: <87v8x7d82o.fsf@yahoo.com> (raw)
In-Reply-To: <83czjguoys.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 21 Feb 2022 19:08:43 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> I reverted that commit.
>
> PROBLEMS is special in that it describes issues with software other
> than Emacs. Since we cannot control that external software, we
> usually cannot know whether and when those issues are resolved, nor
> whether old versions of that software are still being used by someone
> who happens to run a newer Emacs. So the fact that Damien no longer
> sees the problem doesn't mean it cannot happen to someone else,
> because what fixed that for Damien could be upgrade of some software
> (other than Emacs) which other Emacs users don't necessarily share.
>
> For this reason, we almost never can positively know that a PROBLEMS
> entry is no longer relevant, and that is why we have there very old
> entries. (It's possible that some of them can be removed, but the
> rationale should be that we can establish positively that the software
> causing problems is known to not be relevant anymore.)
Yes. This particular bug also depends on the video driver and X server
to a larger degree than normal. Damien could have upgraded his X
server, but other people might be running different versions (or
entirely different servers altogether.)
next prev parent reply other threads:[~2022-02-22 1:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 16:17 bug#30088: 26.0.90; [Emacs 26] Rendering glitch Damien Cassou
2018-01-12 16:22 ` Noam Postavsky
2018-01-15 8:49 ` Damien Cassou
2018-01-24 19:59 ` Charles A. Roelli
2018-01-24 20:10 ` Damien Cassou
2018-01-26 12:33 ` Damien Cassou
2018-01-26 19:38 ` Charles A. Roelli
2018-01-26 20:03 ` Eli Zaretskii
2018-01-27 14:09 ` Charles A. Roelli
2018-01-27 14:14 ` Dmitry Gutov
2018-01-27 15:30 ` Eli Zaretskii
2022-02-21 15:29 ` bug#30088: Rendering glitch with double buffering enabled Lars Ingebrigtsen
2022-02-21 15:45 ` Damien Cassou
2022-02-21 16:04 ` Lars Ingebrigtsen
2022-02-21 17:08 ` Eli Zaretskii
2022-02-22 1:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2018-01-27 15:30 ` bug#30088: 26.0.90; [Emacs 26] Rendering glitch 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=87v8x7d82o.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=30088@debbugs.gnu.org \
--cc=charles@aurox.ch \
--cc=damien@cassou.me \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=npostavs@users.sourceforge.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).