From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.bugs Subject: bug#59727: Problems with displaying long lines Date: Wed, 30 Nov 2022 19:46:37 +0200 Organization: LINKOV.NET Message-ID: <86zgc8e3nm.fsf@mail.linkov.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30847"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/30.0.50 (x86_64-pc-linux-gnu) To: 59727@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Nov 30 18:50:16 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 1p0RDs-0007oC-8e for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 30 Nov 2022 18:50:16 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p0RDg-0004Ct-Ul; Wed, 30 Nov 2022 12:50:04 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p0RDg-0004Cl-8r for bug-gnu-emacs@gnu.org; Wed, 30 Nov 2022 12:50:04 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1p0RDf-0004fE-QX for bug-gnu-emacs@gnu.org; Wed, 30 Nov 2022 12:50:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1p0RDe-0001X9-LK for bug-gnu-emacs@gnu.org; Wed, 30 Nov 2022 12:50:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Juri Linkov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 30 Nov 2022 17:50:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: report 59727 X-GNU-PR-Package: emacs X-Debbugs-Original-To: bug-gnu-emacs@gnu.org Original-Received: via spool by submit@debbugs.gnu.org id=B.16698305845879 (code B ref -1); Wed, 30 Nov 2022 17:50:02 +0000 Original-Received: (at submit) by debbugs.gnu.org; 30 Nov 2022 17:49:44 +0000 Original-Received: from localhost ([127.0.0.1]:34134 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1p0RDL-0001Wl-VK for submit@debbugs.gnu.org; Wed, 30 Nov 2022 12:49:44 -0500 Original-Received: from lists.gnu.org ([209.51.188.17]:38610) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1p0RDJ-0001Wf-DX for submit@debbugs.gnu.org; Wed, 30 Nov 2022 12:49:43 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p0RDI-0004AJ-6i for bug-gnu-emacs@gnu.org; Wed, 30 Nov 2022 12:49:41 -0500 Original-Received: from relay1-d.mail.gandi.net ([217.70.183.193]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p0RDF-0004WR-Pg for bug-gnu-emacs@gnu.org; Wed, 30 Nov 2022 12:49:39 -0500 Original-Received: (Authenticated sender: juri@linkov.net) by mail.gandi.net (Postfix) with ESMTPSA id D336C240003 for ; Wed, 30 Nov 2022 17:49:32 +0000 (UTC) Received-SPF: pass client-ip=217.70.183.193; envelope-from=juri@linkov.net; helo=relay1-d.mail.gandi.net X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:249538 Archived-At: [A new bug report from bug#56682] >> 1. after 'M-g TAB' (move-to-column) to 214748364 or more, >> the display is not updated anymore: moving point to the left >> from this position shows the cursor, moving point to the right >> has no visible effect. Is it a hard limit in the display engine? >> Its hex value is #xccccccc. > > Sounds like a possible bug. Does point move? What does "C-x =" say about > point if you move beyond column 214748364? Point moves correctly: point=214748362 of 1135341900 (19%) column=214748361 Hscroll=214748321 point=214748363 of 1135341900 (19%) column=214748362 Hscroll=214748322 point=214748364 of 1135341900 (19%) column=214748363 Hscroll=214748323 point=214748365 of 1135341900 (19%) column=214748364 Hscroll=214748324 point=214748366 of 1135341900 (19%) column=214748365 Hscroll=214748325 but the cursor motion is not visible. > If you window is auto-hscrolled as result, then there is indeed hard limit: > the X coordinate of a screen line is an 'int', so MAX_INT divided by the > pixel-width of your default font is as far as we can go. Maybe this limitation of auto-hscrolling should be documented? >> 2. after starting Isearch at a large column number, >> Emacs hangs up indefinitely, e.g. with >> 'M-g TAB 10000000 RET C-s' then even C-g doesn't get out. >> Debugging shows that the problem is in 'isearch-update' >> where the call to 'pos-visible-in-window-group-p' doesn't return. >> When this call is removed, the search is instantaneous. >> (Optimizing lazy-highlight is a separate problem in bug#56815.) > > I thought we agreed that calling pos-visible-in-window-p is not a good idea > in this situation, since it will always think any position is visible? Does pos-visible-in-window-p fail only on long lines? >> PS: it seems these problems are not related to the locked narrowing, >> rather the locked narrowing helped to expose them, so maybe they >> should be reported in a new separate bug report? > > It is unrelated, because handling lines that are both very long and > truncated on display uses a separate set of display shortcuts, and locked > narrowing has almost no effect on that. Ok, therefore a new bug report.