From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Unfreezing the display during auto-repeated scrolling. Simpler approach. Date: Wed, 29 Oct 2014 17:37:26 +0200 Message-ID: <83fve628g9.fsf@gnu.org> References: <20141026221530.GF4397@acm.acm> <20141027142801.GC2771@acm.acm> <83y4s1317s.fsf@gnu.org> <20141027193839.GD2771@acm.acm> <20141028181003.GA6630@acm.acm> <83wq7j0xqj.fsf@gnu.org> <20141029145211.GB2953@acm.acm> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1414597082 10385 80.91.229.3 (29 Oct 2014 15:38:02 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 29 Oct 2014 15:38:02 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Oct 29 16:37:55 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XjVJj-0000tv-1w for ged-emacs-devel@m.gmane.org; Wed, 29 Oct 2014 16:37:47 +0100 Original-Received: from localhost ([::1]:46914 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XjVJi-0004ld-M1 for ged-emacs-devel@m.gmane.org; Wed, 29 Oct 2014 11:37:46 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38222) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XjVJZ-0004lK-Su for emacs-devel@gnu.org; Wed, 29 Oct 2014 11:37:43 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XjVJV-0005Cg-7k for emacs-devel@gnu.org; Wed, 29 Oct 2014 11:37:37 -0400 Original-Received: from mtaout20.012.net.il ([80.179.55.166]:45733) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XjVJV-0005CP-0B for emacs-devel@gnu.org; Wed, 29 Oct 2014 11:37:33 -0400 Original-Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0NE700C00Q087000@a-mtaout20.012.net.il> for emacs-devel@gnu.org; Wed, 29 Oct 2014 17:37:31 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NE700BYSQ2IX440@a-mtaout20.012.net.il>; Wed, 29 Oct 2014 17:37:30 +0200 (IST) In-reply-to: <20141029145211.GB2953@acm.acm> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.166 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:176013 Archived-At: > Date: Wed, 29 Oct 2014 14:52:11 +0000 > Cc: Stefan Monnier , emacs-devel@gnu.org > From: Alan Mackenzie > > On Wed, Oct 29, 2014 at 04:14:12PM +0200, Eli Zaretskii wrote: > > > From: Stefan Monnier > > > Date: Tue, 28 Oct 2014 20:57:16 -0400 > > > Cc: Eli Zaretskii , emacs-devel@gnu.org > > > > I'm beginning to like your C-level hack. > > > And I still dislike it. > > Just to be absolutely clear, we're talking about my _simpler_ hack, the > one that binds fontification-functions to nil during scrolling. I didn't realize that, thanks for clarifying. Yes, that's better. > ONLY when the user option (precise mechanism not yet worked out) > use-default-face-for-fast-scrolling is non-nil. As long as CC Mode doesn't set that by default, I can live with that. > By suggesting the use of jit-lock-defer, somehow, to speed up scrolling, > the principle that scrolled over buffer regions MUST be fontified has > been given up. That wasn't my reasoning, it was the opposite: _if_ we are willing to accept that the scrolled-over parts be unfontified, _then_ we already have an optional feature which does precisely that. > I'm guessing you still accept that the problem (frozen screen during and > after auto-repeated scrolling) needs to be solved. Yes, but (a) it is IMO not a very important use case, and (b) the best way to solve it is where it is caused, i.e. in CC Mode. Otherwise, we are on a slippery slope: here is the mode that succeeds in wedging redisplay, and we are "solving" it by disabling important parts of the display engine. No offense, but that's tail wagging the dog. Next time another mode will come up with the same problem, what do we say to ask the author/maintainer to get their act together? > What do you think? Given that no one is willing to do (what I think is) TRT, I guess your suggestion is something we can live with, as long as that variable is off by default.