all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alan Third <alan@idiocy.org>
Cc: 45038@debbugs.gnu.org, Emacs-hacker2018@jovi.net, stefan@marxist.se
Subject: bug#45038: 27.1; blank display
Date: Fri, 04 Dec 2020 15:25:40 +0200	[thread overview]
Message-ID: <83czzpem97.fsf@gnu.org> (raw)
In-Reply-To: <X8o1fQ/IEkVcilXR@breton.holly.idiocy.org> (message from Alan Third on Fri, 4 Dec 2020 13:11:25 +0000)

> Date: Fri, 4 Dec 2020 13:11:25 +0000
> From: Alan Third <alan@idiocy.org>
> Cc: stefan@marxist.se, 45038@debbugs.gnu.org, Emacs-hacker2018@jovi.net
> 
> > If it isn't reasonable to release Emacs 27.2 with this problem, we may
> > wish backporting the change even though it is large.
> > 
> > How easy is it to bump into this problem, and is there an easy
> > workaround when you do?
> 
> It's unusual to have the display completely blanking, most people just
> see small localised glitches. Usually it can be solved by forcing a
> redisplay of some sort, which is what you can see in Devon's example
> as he moves the cursor across the lines, which forces redisplay of
> those lines.
> 
> I would prefer not to back-port to Emacs 27, but if you think it's
> necessary I'll give it a go.

Given the rarity of the situation and the easy workaround, I agree
that backporting is not required.

Thanks.





  reply	other threads:[~2020-12-04 13:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-04  3:33 bug#45038: 27.1; blank display Devon Sean McCullough
2020-12-04  8:10 ` Stefan Kangas
2020-12-04  8:31 ` Eli Zaretskii
2020-12-04  8:45   ` Stefan Kangas
2020-12-04 10:53     ` Alan Third
2020-12-04 12:02       ` Eli Zaretskii
2020-12-04 13:11         ` Alan Third
2020-12-04 13:25           ` Eli Zaretskii [this message]
2021-04-29 16:49       ` Stefan Kangas
2021-10-11 12:13         ` Stefan Kangas

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=83czzpem97.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=45038@debbugs.gnu.org \
    --cc=Emacs-hacker2018@jovi.net \
    --cc=alan@idiocy.org \
    --cc=stefan@marxist.se \
    /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.