From: Eli Zaretskii <eliz@gnu.org>
To: Fabrice Popineau <fabrice.popineau@gmail.com>
Cc: 39188@debbugs.gnu.org
Subject: bug#39188: 28.0.50; w32 cursor redisplay problem
Date: Sun, 19 Jan 2020 18:11:25 +0200 [thread overview]
Message-ID: <83wo9nxw7m.fsf@gnu.org> (raw)
In-Reply-To: <CAFgFV9Munmmq=tbFq=oNhX35egsXcaG75HwHqGbw0YSiyyGLMg@mail.gmail.com> (message from Fabrice Popineau on Sun, 19 Jan 2020 16:39:56 +0100)
> From: Fabrice Popineau <fabrice.popineau@gmail.com>
> Date: Sun, 19 Jan 2020 16:39:56 +0100
> Cc: 39188@debbugs.gnu.org
>
> Please show a reproduction recipe starting from "emacs -Q". Your
> image seems to show a trace on every line, which is not what I see
> here. What I see here is 2 artefacts: one in the middle of the
> window, another at its beginning, and this problem seems to have
> started with Emacs 25.1, not a few months ago.
>
> From what I tried, it is not completely deterministic (or it depends on many parameters).
> Best bet to reproduce the problem: visit some long org file like or-manual.org from the org distribution,
> with 'emacs -Q',
> use C-S-tab 3 times to expand all headings
> and run sequences of C-n and C-p to force scrolling of the buffer.
> You should see those artefacts at some point.
Sorry, I don't. I only see one or 2 artefacts in the window, as I
described.
next prev parent reply other threads:[~2020-01-19 16:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 9:17 bug#39188: 28.0.50; w32 cursor redisplay problem Fabrice Popineau
2020-01-19 15:22 ` Eli Zaretskii
2020-01-19 15:39 ` Fabrice Popineau
2020-01-19 16:11 ` Eli Zaretskii [this message]
2020-01-19 16:32 ` Fabrice Popineau
2020-01-19 16:47 ` Eli Zaretskii
2020-01-19 17:29 ` Fabrice Popineau
2020-01-20 17:19 ` Eli Zaretskii
2020-01-20 18:41 ` Fabrice Popineau
2020-01-21 16:32 ` Eli Zaretskii
2020-01-21 16:36 ` Fabrice Popineau
2020-01-21 16:59 ` 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=83wo9nxw7m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39188@debbugs.gnu.org \
--cc=fabrice.popineau@gmail.com \
/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).