Re: Unfreezing the display during auto-repeated scrolling. Simpler approach.

[Eli Zaretskii]

> From: Stefan Monnier <address@hidden>
> Cc: Eli Zaretskii <address@hidden>,  address@hidden
> Date: Thu, 30 Oct 2014 23:06:09 -0400
> 
> > Who's going to decide when a "forced" display is to take place?
> 
> That's the question, indeed.  Maybe we could simply move the
> `input-pending' test so it's done before running the command.  I.e. if
> there was no input pending when the command started, then don't skip
> the redisplay.

I hope the intent is that this behavior will be optional, and by
default turned off.  If not, I'm going to object to such a change.

Remember, all this was triggered by a single use case: leaning on the
PageDown (or C-v or M-v) key.  IMO, this use case is not very
important, although others might disagree.  In any case, changing the
way redisplay works by default due to this use case makes little sense
to me.

(Apologies if I lost track of what exactly you are discussing here.)