From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: kcbanner@gmail.com, 59320@debbugs.gnu.org
Subject: bug#59320: Acknowledgement (29.0.50; (Windows) Cursor is invisble unless inhibit-double-buffer is t, and then it only appears as a single pixel line)
Date: Wed, 23 Nov 2022 15:44:02 +0200 [thread overview]
Message-ID: <83bkoxzsyl.fsf@gnu.org> (raw)
In-Reply-To: <87ilj633i4.fsf@yahoo.com> (message from Po Lu on Wed, 23 Nov 2022 08:42:43 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: Casey Banner <kcbanner@gmail.com>, 59320@debbugs.gnu.org
> Date: Wed, 23 Nov 2022 08:42:43 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > So I guess we should disable double-buffering on Windows when system caret
> > is in use?
>
> I'd only do that if all else fails. How does MS-Windows display the
> system caret, and why can't it be made to work with double-buffering?
I don't know the answer to the second part, but if you search the C sources
for w32_use_visible_system_caret, you will probably see the answer right
away (there aren't many hits).
next prev parent reply other threads:[~2022-11-23 13:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 16:25 bug#59320: 29.0.50; (Windows) Cursor is invisble unless inhibit-double-buffer is t, and then it only appears as a single pixel line Casey Banner
2022-11-17 2:07 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-17 2:48 ` Visuwesh
2022-11-17 3:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <handler.59320.B.16686321866422.ack@debbugs.gnu.org>
2022-11-22 4:01 ` bug#59320: Acknowledgement (29.0.50; (Windows) Cursor is invisble unless inhibit-double-buffer is t, and then it only appears as a single pixel line) Casey Banner
2022-11-22 13:19 ` Eli Zaretskii
2022-11-23 0:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-23 13:44 ` Eli Zaretskii [this message]
2022-11-23 13:54 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-22 16:29 ` bug#59320: Casey Banner
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=83bkoxzsyl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59320@debbugs.gnu.org \
--cc=kcbanner@gmail.com \
--cc=luangruo@yahoo.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.