unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Fabrice Popineau <fabrice.popineau@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 39188-done@debbugs.gnu.org
Subject: bug#39188: 28.0.50; w32 cursor redisplay problem
Date: Tue, 21 Jan 2020 17:36:13 +0100	[thread overview]
Message-ID: <CAFgFV9P4fxwWz-O+oQ6+XwH+Kv_kUd41P64_MMjERE-28sxi7g@mail.gmail.com> (raw)
In-Reply-To: <838sm0wz0p.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]

Great, thanks!

Only you can find this quickly.

Fabtice

Le mar. 21 janv. 2020 à 17:32, Eli Zaretskii <eliz@gnu.org> a écrit :

> > From: Fabrice Popineau <fabrice.popineau@gmail.com>
> > Date: Mon, 20 Jan 2020 19:41:48 +0100
> > Cc: 39188@debbugs.gnu.org
> >
> > Maybe it is not the most important bug (except if Windows start to tell
> > emacs that there are screen readers everywhere)
>
> I found the problem.  As part of redisplay, we sometimes scroll
> rectangular portions of the window, as pixels, up and down.  When we
> do so, we first turn off the cursor, but when the system caret is used
> instead of the cursor, we hide and unhide the caret in a separate UI
> thread.  So there's a race between the main thread which scrolls the
> pixels and the UI thread that draws the caret, and that race causes
> the pixels of the caret to sometimes be copied with the rectangular
> area that is scrolled.
>
> The solution is to disable the scrolling in w32_scroll_run when the
> system caret is in use.  This slows down redisplay to some extent
> (because w32_scroll_run is a redisplay optimization), but I don't see
> any easy way around that.
>
> Should be fixed now on the emacs-27 branch.
>

[-- Attachment #2: Type: text/html, Size: 1810 bytes --]

  reply	other threads:[~2020-01-21 16:36 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
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 [this message]
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=CAFgFV9P4fxwWz-O+oQ6+XwH+Kv_kUd41P64_MMjERE-28sxi7g@mail.gmail.com \
    --to=fabrice.popineau@gmail.com \
    --cc=39188-done@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).