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: Thu, 21 Jul 2022 20:15:55 +0000 Message-ID: References: <87h73ab8bo.fsf@gmail.com> <83zgh2kzlo.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="31SQA5rcgw" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="32383"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 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 Thu Jul 21 22:22:01 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 1oEcgL-0008GI-4v for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 21 Jul 2022 22:22:01 +0200 Original-Received: from localhost ([::1]:38442 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oEcgJ-00007S-OM for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 21 Jul 2022 16:21:59 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42784) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oEcaZ-0000br-1y for bug-gnu-emacs@gnu.org; Thu, 21 Jul 2022 16:16:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:49555) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oEcaY-0001Ap-Oz for bug-gnu-emacs@gnu.org; Thu, 21 Jul 2022 16:16:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oEcaY-0008R0-E7 for bug-gnu-emacs@gnu.org; Thu, 21 Jul 2022 16:16: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: Thu, 21 Jul 2022 20:16: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.165843455932407 (code B ref 56683); Thu, 21 Jul 2022 20:16:02 +0000 Original-Received: (at 56683) by debbugs.gnu.org; 21 Jul 2022 20:15:59 +0000 Original-Received: from localhost ([127.0.0.1]:39304 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oEcaV-0008Qd-4K for submit@debbugs.gnu.org; Thu, 21 Jul 2022 16:15:59 -0400 Original-Received: from heytings.org ([95.142.160.155]:47082) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oEcaT-0008QT-FZ for 56683@debbugs.gnu.org; Thu, 21 Jul 2022 16:15:58 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1658434555; bh=3F+6Md+54dMg3hNOlssHyqhyD2QT0vRSC53YtghJ/cs=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=lH6+1AUWWYoCsMzTX98OGg9XYy1AZmqjcAyEPVv8cXDXjwAguYewcNmujr2uyxrZa 6buUNVNhcq6JXZRburMVy3eFTJBjIfCtm8vR5+QctrB7jkF2jJyuYKHPZj6J8ez4nX Xxy0N4Uvl9z6szF5rGsb6ClLcwJJy6Lk62sxfhcPCYhvIX26PipaKp6cm7SXwpP7si aKBKadGLf/jKOjGzp5UUquysa1oUlqvqK+KIFwYrHEgZH5IoSQErQ9xZ7L6W6A44N8 AtHYINIoy/lld6enoRWk+Y2xWZArmHRz2q/4GMVpnVpbLrpVEP170E8WNIKpqdBazd 8J7PWlYXVU9Qg== In-Reply-To: <83zgh2kzlo.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:237573 Archived-At: --31SQA5rcgw Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable > > Is this related to the below (from xdisp.c)? > > #define DISP_INFINITY 10000000 > > Maybe we should make "infinity" somewhat larger? dictionary.json has a= =20 > single line that is 18922365 characters long, so it's "more than=20 > infinity". > It is indeed, setting DISP_INFINITY to 1000000000 "fixes" that bug.=20 But... how infinite is infinite? (A near-philosophical question =F0=9F=98= =89)=20 With a somewhat larger file (that one is only 20 MB) we'd have to increase= =20 it again. If that's a hard-coded limit, I guess it's a sign that we=20 should advise against using toggle-truncate-lines in buffer with long=20 lines. --31SQA5rcgw--