"Eli Zaretskii" <[EMAIL PROTECTED]> writes: >> Cc: emacs-devel@gnu.org >> From: David Kastrup <[EMAIL PROTECTED]> >> Date: Wed, 27 Apr 2005 11:43:01 +0200 >> >> We are talking about the situation where the input is coming in faster >> than Emacs can process it. > > See, we don't really know that. Whether this is true or not, > depends on several unknown factors, like the rate of keyboard > auto-repeat on the user's machine vs the time it takes Emacs on that > machine, with that CPU and display type/toolkit to perform > redisplay. > > In my experience, movement with C-n gives Emacs enough time to > update the display.
The last time I looked, this thread was about Emacs not being fast enough to update the display. > jit-lock-defer-time non-nil works by disabling fontification > altogether until Emacs is idle. If fontification is not disabled, > you yourself explained that vertical-motion _must_ fontify to keep > its calculations accurate. It seems I am a complete failure at conveying my meaning. I was arguing for a setting where vertical-motion is allowed to keep its calculations inaccurate with regard to font locking. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum _______________________________________________ Emacs-devel mailing list Emacs-devel@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-devel
