[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: input-pending-p after make-frame-visible

From: Eli Zaretskii
Subject: Re: input-pending-p after make-frame-visible
Date: Thu, 21 Oct 2021 10:47:58 +0300

> Date: Thu, 21 Oct 2021 15:58:39 +0900
> From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
> Cc: Eli Zaretskii <eliz@gnu.org>,
>       martin rudalics <rudalics@gmx.at>,
>       Alan Third <alan@idiocy.org>,
>       Gregory Heytings <gregory@heytings.org>,
>       emacs-devel@gnu.org
> > > The original code included conditions
> > > that depend on use of the toolkit scroll bars (the reasons for which
> > > we don't understand, AFAICT) and ignored just a small group of events,
> > > now we will/might ignore much more, and that's in the main source of
> > > reading events.  Who knows what this will do.
> > 
> > Yeah, that part is the biggest head scratcher to me. I wonder if
> > Yamamoto Mitsuharu may know why this was added this way in
> > 354344a20a06e2052bc23a4b92ac44af1075cdbe
> Maybe I've injected some bug with the above change?  The original
> intention was to coalesce redisplays caused by successive scroll thumb
> dragging events because otherwise we only see partly updated screen
> when redisplay-dont-pause is nil, which used to be the default.
> See https://lists.gnu.org/r/emacs-devel/2005-05/msg00297.html .

Thanks.  With this explanation, I think we do need a new flag, and we
should use it controlled by some variable exposed to Lisp.  If this
proves not to have adverse effects, we can in the future discard that
variable and make the additional filtering unconditional.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]