unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: HaiJun Zhang <netjune@outlook.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Need help to debug bugs(#22989, #23412)
Date: Sun, 27 Oct 2019 07:00:04 +0000	[thread overview]
Message-ID: <PS1PR03MB3606494B25EDD7031494FA9DB7670@PS1PR03MB3606.apcprd03.prod.outlook.com> (raw)
In-Reply-To: <8336feu4k7.fsf@gnu.org>

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

在 2019年10月27日 +0800 PM1:43,Eli Zaretskii <eliz@gnu.org>,写道:
If your analysis is correct, then maybe input methods (or their users,
if you mean a non-Emacs input method) should set redisplay-dont-pause
nil, and we should un-obsolete that variable.

Yes, non-Emacs input method.

Setting redisplay-dont-pause to t causes other problem for emacs after 26.2, which is worse than this one.
See https://lists.gnu.org/archive/html/emacs-devel/2019-01/msg00495.html

But the question is: do both events you mention arrive with any time
interval between them, or do they arrive together? IOW, the issue is
about timing, not about the number of events.

Yes, agreed.

Maybe the first redisplay is interrupted by the second event when redisplay-dont-pause is nil. And the result of the first redisplay doesn’t show on screen. So no flicker.  It is just my guess.


You mean, print in C? You can use the safe_debug_print function.
Yes. Thanks.


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

  reply	other threads:[~2019-10-27  7:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <21859cd7-8e0a-4fe4-952e-b0a94305a573@Spark>
2019-10-27  3:10 ` Need help to debug bugs(#22989, #23412) HaiJun Zhang
2019-10-27  5:23   ` HaiJun Zhang
2019-10-27  5:43   ` Eli Zaretskii
2019-10-27  7:00     ` HaiJun Zhang [this message]
2019-10-27  7:12       ` Eli Zaretskii
2019-10-27  8:39         ` HaiJun Zhang
2019-10-27 11:43         ` HaiJun Zhang
2019-10-27  7:12     ` HaiJun Zhang

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=PS1PR03MB3606494B25EDD7031494FA9DB7670@PS1PR03MB3606.apcprd03.prod.outlook.com \
    --to=netjune@outlook.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).