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#56393: Actually fix the long lines display bug Date: Wed, 20 Jul 2022 09:08:22 +0000 Message-ID: <7d422ac79b0dec11e4ea@heytings.org> References: <38c1a31040d2d2bc47ae@heytings.org> <83a695nugr.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15563"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , 56393@debbugs.gnu.org To: Gerd =?UTF-8?Q?M=C3=B6llmann?= Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Jul 20 11:36:54 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 1oE68U-0003mL-E4 for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 20 Jul 2022 11:36:54 +0200 Original-Received: from localhost ([::1]:49362 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oE68T-00068g-Fp for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 20 Jul 2022 05:36:53 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59914) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oE5hX-0000S3-HM for bug-gnu-emacs@gnu.org; Wed, 20 Jul 2022 05:09:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:58078) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oE5hW-0002Ek-4g for bug-gnu-emacs@gnu.org; Wed, 20 Jul 2022 05:09:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oE5hW-000664-0K for bug-gnu-emacs@gnu.org; Wed, 20 Jul 2022 05:09: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: Wed, 20 Jul 2022 09:09:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 56393 X-GNU-PR-Package: emacs Original-Received: via spool by 56393-submit@debbugs.gnu.org id=B56393.165830810623346 (code B ref 56393); Wed, 20 Jul 2022 09:09:01 +0000 Original-Received: (at 56393) by debbugs.gnu.org; 20 Jul 2022 09:08:26 +0000 Original-Received: from localhost ([127.0.0.1]:55833 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oE5gw-00064T-2n for submit@debbugs.gnu.org; Wed, 20 Jul 2022 05:08:26 -0400 Original-Received: from heytings.org ([95.142.160.155]:45038) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oE5gu-00064I-Po for 56393@debbugs.gnu.org; Wed, 20 Jul 2022 05:08:25 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1658308103; bh=yxIwGYFP82ylXDDmjdfVmqw8lCgxlqVa14JyT7wtJUI=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=Yl+tB+5q5A2mfSqw5i0lrKLF7yp1MEdg0JQqPma/TqbGwbgTXsFVi2OCmIuU7oyJr o3/sZ5eDZEhn+UVVecwcnLVpmHpbtVvYq/mvi2W73TEJsgbazdpibdyf0LN2f6rGq5 5FMOaUUBEAa/2bOK794yFIFVQxyS7nDtkAQDIoS0An4YeY5RDODxnrH6Q2MWH1GLso syer0HQSMILiupnY6EfKiPlUPFwgI4ojl3JOGXi3+UGnAsrINh5xMcJab8q2WGbrZl 6hVhiT389sQrQ09oIUkd86eq72vimOaLszXvI5w/uaJh2T2DQ7jEvrIDbydsDgdxgI ECMzgBLqLgCaA== In-Reply-To: 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:237485 Archived-At: > > It was mentioned a number of times that only a small fraction of people > encounter that problem. And I'd add that this small fraction encounters > the problem only in a small fraction of cases. And I even think most of > these cases are known upfront. > I agree that it's a relatively rare problem, but when it happens it is very annoying, because Emacs becomes unusable. I disagree, however, that most of theses cases are known upfront, in most cases a user simply opens a file that they can open in other editors without setting any specific option in these other editors, with the expectation that they will be able to edit it in Emacs. Now the situation is reversed: you can open and edit files in Emacs that you cannot open and edit in other editors. > > So, with some kind of mode, one could turn the iterator-narrowing on > (and off!) in redisplay_window without affecting anyone who doesn't have > the problem in the first place. > What we have right now is a kind of (minimal) mode indeed, which is turned on automatically when necessary. And from a user point of view it's also a kind of (minimal) mode, which they can turn off unconditionally by setting long-line-threshold to nil in their init file, or turn on unconditionally by setting long-line-threshold to 0 in their init file. I don't think turning it on unconditionally has any significant drawback, but there some extreme cases where commands would not do their job properly (for example, doing M-> C-u 37000 C-p in xdisp.c), which is why it is not turned on unconditionally by default.