From: charles@aurox.ch (Charles A. Roelli)
To: Damien Cassou <damien@cassou.me>
Cc: 30088@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#30088: 26.0.90; [Emacs 26] Rendering glitch
Date: Wed, 24 Jan 2018 20:59:58 +0100 [thread overview]
Message-ID: <m27es7c9j5.fsf@aurox.ch> (raw)
In-Reply-To: <87lggzecb8.fsf@cassou.me> (message from Damien Cassou on Mon, 15 Jan 2018 09:49:47 +0100)
> From: Damien Cassou <damien@cassou.me>
> Date: Mon, 15 Jan 2018 09:49:47 +0100
>
> Noam Postavsky <npostavs@users.sourceforge.net> writes:
> > On Fri, Jan 12, 2018 at 11:17 AM, Damien Cassou <damien@cassou.me> wrote:
> >> Please see attached screenshot. I regularly get that kind of glitches in
> >> all kinds of buffers. I didn't try to reproduce with Emacs -Q.
> >
> > Does disabling double buffering help? It looks similar to what's
> > described in Bug#29416.
>
> Thanks for your answer. I have changed my WM and am waiting for the
> problem to reappear before trying your workaround.
Any news on this? Could you please try the recipe in Bug#29416 to see
if you have the same problem?
next prev parent reply other threads:[~2018-01-24 19:59 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 [this message]
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
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=m27es7c9j5.fsf@aurox.ch \
--to=charles@aurox.ch \
--cc=30088@debbugs.gnu.org \
--cc=damien@cassou.me \
--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).