From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings Newsgroups: gmane.emacs.bugs Subject: bug#56683: 29.0.50; long lines fix doesn't work correctly when lines are truncated Date: Tue, 26 Jul 2022 20:14:14 +0000 Message-ID: References: <87h73ab8bo.fsf@gmail.com> <83zgh2kzlo.fsf@gnu.org> <83y1wlllnc.fsf@gnu.org> <83mtd1li6o.fsf@gnu.org> <835yjpl5vm.fsf@gnu.org> <83y1wljmkn.fsf@gnu.org> <83r12djjvm.fsf@gnu.org> <8a3eaeef01b9a103450a@heytings.org> <835yjkdrrk.fsf@gnu.org> <83r128cane.fsf@gnu.org> <83h734c8wx.fsf@gnu.org> <834jz3dbva.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36058"; mail-complaints-to="usenet@ciao.gmane.io" Cc: gerd.moellmann@gmail.com, andreyorst@gmail.com, 56683@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Jul 26 22:56:37 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1oGRbY-00099f-Hd for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 26 Jul 2022 22:56:36 +0200 Original-Received: from localhost ([::1]:35158 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oGRbX-0003Bb-I8 for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 26 Jul 2022 16:56:35 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59174) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oGQxK-00066S-Rq for bug-gnu-emacs@gnu.org; Tue, 26 Jul 2022 16:15:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:36468) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oGQxK-0001dl-Eo for bug-gnu-emacs@gnu.org; Tue, 26 Jul 2022 16:15:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oGQxK-000639-9G for bug-gnu-emacs@gnu.org; Tue, 26 Jul 2022 16:15:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Gregory Heytings Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 26 Jul 2022 20:15:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 56683 X-GNU-PR-Package: emacs Original-Received: via spool by 56683-submit@debbugs.gnu.org id=B56683.165886646023176 (code B ref 56683); Tue, 26 Jul 2022 20:15:02 +0000 Original-Received: (at 56683) by debbugs.gnu.org; 26 Jul 2022 20:14:20 +0000 Original-Received: from localhost ([127.0.0.1]:54450 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oGQwd-00061k-Us for submit@debbugs.gnu.org; Tue, 26 Jul 2022 16:14:20 -0400 Original-Received: from heytings.org ([95.142.160.155]:54024) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oGQwa-00061U-2e for 56683@debbugs.gnu.org; Tue, 26 Jul 2022 16:14:17 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1658866454; bh=YFk3UhxmMX21Sd/iqcZwtMIngIIWhfu0K1o6q79Inng=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=QYXbUrsQR1ipk626F8T91d1ec/M/dO+vZVlJSt4c8yqOOtv/zpjCubnkQJ0XMosVG FvKgOpncIZrZyKhE4cReAcep0nl4uOVqL5BPv61cQ4e8oRb3rYYLGiv4Ra3v3SVqaY rn3YrFf0FgzW4Kwo8B163hZtwFP35gb+K9xq6CsP6S61Pg6baQNlU1RCePNd1qhebb yEgebmQLBZeOdWQLbpZ3p7TaUj+g05Dmy9Dixd9B2ziw5pkdN3oLB3uoJ2ebL1yzFN LnLfnWnGpckjtssxy4Ma0tN9HU6eV+T69RA8QW94SbG25awkw7GrvOhkCiJrPbepsU U5wlQ9MSZJ73w== In-Reply-To: <834jz3dbva.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:237988 Archived-At: > > My feeling is that we didn't yet exhaust the potential for speedups by > ways other than by turning off features. > My feeling is that we did, if we take the truncate-lines case out of the picture. My feeling is also that adding more optimizations for the truncate-lines case is not worth the price. > > The font-lock effect is a good case in point: if we were to decide to > turn it off when there are long lines, we'd have missed the speedup you > just installed. > The difference is that I told you that I would look at that problem, and that now, after having spent many hours on this, I highly doubt it's possible to do better, especially given that no matter what we do to improve the truncate-lines case, we'll hit another ceil very soon (the DISP_INFINITY one, even if you decide to enlarge it). It seems to me that the most reasonable thing to do is to simply tell users that Emacs has a limit in that case (and again, it has one, no matter what we do). As far as I can see, the only way to really speedup the truncate-lines case would be to introduce an entirely new narrowing method, in which the buffer would be narrowed in a rectangular way. That is, instead of narrowing a buffer between BEGV and ZV, each line 1, ..., n around point would be narrowed between BEGV1..ZV1, ..., BEGVn..ZVn. > > truncate-lines is an important feature (we just heard someone explaining > one such use case), > In that specific use case the lines do not hit the long-line-threshold limit.