From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: emacs rendering comparisson between emacs23 and emacs26.3 Date: Mon, 06 Apr 2020 18:30:57 +0300 Message-ID: <83369gskb2.fsf@gnu.org> References: <834ku43c61.fsf@gnu.org> <83k12zz6ds.fsf@gnu.org> <054393f3-3873-ab6e-b325-0eca354d8838@gmx.at> <20200403174757.GA8266@ACM> <20200404104553.GA5329@ACM> <07fe3b69-3ab2-3173-0696-cb17809e2b91@gmx.at> <83blo7v68b.fsf@gnu.org> <1845d7aa-9ae4-3d95-6a30-c7b1d8d8adec@gmx.at> <83a73qt6zs.fsf@gnu.org> <97c4254e-ff43-8402-3645-f713c408c245@gmx.at> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="46593"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rudalics@gmx.at, rrandresf@gmail.com, emacs-devel@gnu.org, rms@gnu.org, acm@muc.de To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Apr 06 17:32:02 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jLTjG-000C12-Ch for ged-emacs-devel@m.gmane-mx.org; Mon, 06 Apr 2020 17:32:02 +0200 Original-Received: from localhost ([::1]:33858 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jLTjF-0005qm-BY for ged-emacs-devel@m.gmane-mx.org; Mon, 06 Apr 2020 11:32:01 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42804) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jLTiV-0004zg-VE for emacs-devel@gnu.org; Mon, 06 Apr 2020 11:31:16 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:32951) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1jLTiV-0006H3-8a; Mon, 06 Apr 2020 11:31:15 -0400 Original-Received: from [176.228.60.248] (port=3561 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jLTiJ-0000w2-Mv; Mon, 06 Apr 2020 11:31:04 -0400 In-Reply-To: (message from Stefan Monnier on Mon, 06 Apr 2020 11:25:43 -0400) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:246534 Archived-At: > From: Stefan Monnier > Cc: acm@muc.de, Eli Zaretskii , rrandresf@gmail.com, > rms@gnu.org, emacs-devel@gnu.org > Date: Mon, 06 Apr 2020 11:25:43 -0400 > > >> 16s in one case a "10 seconds freeze": it sounds to me like you *do* > >> reproduce the problem. > > Not really. In the 16s case redisplay kicks in and displays the buffer > > 250 times. In the 10s case redisplay stops after five times. > > Yes, but the underlying problem remains: it takes 10-16s to do the work, > so if the corresponding input events come in over a period shorter than > 10-16s Emacs won't be able to keep up. I think "the work" of a single scroll-up takes less (much less) than 10-16s. But when several C-v keypresses accumulate (because the user types them faster than Emacs can process them), their collective work takes a long time to process. > The text gets fontified by the scrolling routine because the size of the > text depends on the fontification, so correct scrolling needs to fontify > the text before it can compute the destination of the scroll. > > That's where `fast-but-imprecise-scrolling` comes into play. Right.