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:47:25 +0200 [thread overview]
Message-ID: <83r1zvxujm.fsf@gnu.org> (raw)
In-Reply-To: <CAFgFV9O6cWcc3k43FmYCfJUptmwR5eZEMdFPrU_VGYxCD=jGCg@mail.gmail.com> (message from Fabrice Popineau on Sun, 19 Jan 2020 17:32:17 +0100)
> From: Fabrice Popineau <fabrice.popineau@gmail.com>
> Date: Sun, 19 Jan 2020 17:32:17 +0100
> Cc: 39188@debbugs.gnu.org
>
> Sorry, I don't. I only see one or 2 artefacts in the window, as I
> described.
>
> I should have added : try the cursor in column 12 or so, not at bol.
That's what I did.
> Like the one after Summary here? The cursor being at Manual, 1st line.
> What is annoying is that it gets worse with my usual setting. It seems like
> a race condition with something else.
It's "your usual case" that I cannot reproduce. I only see 1 or 2
traces in a window. I'll try to see how to avoid those traces, but no
promises, as I know almost nothing about the Windows GUI programming.
> OTOH and luckily, there is nothing like that if w32-use-visible-system-caret is set to nil.
I actually am surprised you are using that, it's main use case is for
people who use a speech synthesizer.
next prev parent reply other threads:[~2020-01-19 16:47 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r1zvxujm.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 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.