From: Eli Zaretskii <eliz@gnu.org>
To: Mark Oteiza <mvoteiza@udel.edu>
Cc: emacs-devel@gnu.org
Subject: Re: 2 release blocking bugs left for 25.1!
Date: Tue, 28 Jun 2016 19:30:13 +0300 [thread overview]
Message-ID: <83y45pwa22.fsf@gnu.org> (raw)
In-Reply-To: <87shvy9g25.fsf@udel.edu> (message from Mark Oteiza on Mon, 27 Jun 2016 22:56:50 -0400)
> From: Mark Oteiza <mvoteiza@udel.edu>
> Date: Mon, 27 Jun 2016 22:56:50 -0400
>
> Paul Eggert <eggert@cs.ucla.edu> writes:
>
> > I have recently been running into what appears to be a new display bug
> > with emacs-25 on an xterm display and just now got around to filing a
> > bug report (Bug#23819). Dunno how to fix it offhand, or even to
> > reproduce it reliably alas (perhaps someone with tty display expertise
> > can look into it?). It'd be nice if Emacs 25 didn't have this
> > regression, as it's confusing when the display gets trashed.
>
> Likely not related, but Bug#21177 is a regression I experience that
> results in frequent display corruption.
I proposed some tests for digging into these tricky problems, and I'm
still waiting for someone to pick up the gauntlet.
TIA
prev parent reply other threads:[~2016-06-28 16:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-18 16:54 2 release blocking bugs left for 25.1! John Wiegley
2016-06-18 17:22 ` Eli Zaretskii
2016-06-18 17:24 ` John Wiegley
2016-06-18 17:38 ` Eli Zaretskii
2016-06-20 9:25 ` Nicolas Petton
2016-06-20 12:21 ` Phillip Lord
2016-06-20 23:26 ` John Wiegley
2016-06-21 11:40 ` Phillip Lord
2016-06-21 12:07 ` Stefan Monnier
2016-06-21 18:43 ` John Wiegley
2016-06-21 18:51 ` Eli Zaretskii
2016-06-21 20:14 ` John Wiegley
2016-06-21 20:43 ` Phillip Lord
2016-06-21 21:55 ` Óscar Fuentes
2016-06-22 17:25 ` Phillip Lord
2016-06-22 2:14 ` Paul Eggert
2016-06-28 2:56 ` Mark Oteiza
2016-06-28 16:30 ` Eli Zaretskii [this message]
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=83y45pwa22.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mvoteiza@udel.edu \
/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.