unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 55193@debbugs.gnu.org
Subject: bug#55193: 29.0.50; Double-buffering on MS-Windows freezes cursor in minibuffer
Date: Sat, 30 Apr 2022 18:55:24 +0800	[thread overview]
Message-ID: <8735huu9gj.fsf@yahoo.com> (raw)
In-Reply-To: <83r15e9a07.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 30 Apr 2022 12:49:12 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> The new double-buffering feature on MS-Windows causes unpleasant side
> effect when the user types something into the minibuffer, then presses
> RET to submit and exit the minibuffer.  Without double-buffering, the
> cursor moves to the beginning of the minibuffer, thus providing visual
> feedback that whatever the user typed was submitted.  With
> double-buffering turned on, the cursor "freezes" in its last position,
> at the end of the minibuffer text, until the command finishes and
> redisplay does its job.  Which could be a tangible amount of time,
> during which Emacs looks "frozen".
>
> To reproduce:
>
>   emacs -Q
>   M-x blink-cursor-mode RET
>   C-x C-f src/xdisp.c RET
>
> Observe that the cursor is at the end of the file name until such time
> as xdisp.c is displayed, which could be a second or two in a
> non-optimized build of Emacs.
>
> Can this be avoided, please, i.e. can we update the display after the
> cursor is moved?

Thanks, should be fixed now.





  reply	other threads:[~2022-04-30 10:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-30  9:49 bug#55193: 29.0.50; Double-buffering on MS-Windows freezes cursor in minibuffer Eli Zaretskii
2022-04-30 10:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-04-30 11:07   ` 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=8735huu9gj.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=55193@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --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 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).