From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#56682: locked narrowing Date: Wed, 30 Nov 2022 19:34:28 +0200 Message-ID: <83cz94jqhn.fsf@gnu.org> References: <83r11gdrr4.fsf@gnu.org> <83edxfds7s.fsf@gnu.org> <83r11fc80o.fsf@gnu.org> <83o7wjc6o2.fsf@gnu.org> <83lernc5gu.fsf@gnu.org> <83k076dd7d.fsf@gnu.org> <83czcyd8jf.fsf@gnu.org> <83a682d66r.fsf@gnu.org> <837d36ceno.fsf@gnu.org> <37dd2827f54f8bbda5e3@heytings.org> <735c1d5b-0d64-a8e1-3aaa-91fc0248abd3@yandex.ru> <86cz94jxwo.fsf@mail.linkov.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="799"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 56682@debbugs.gnu.org, gregory@heytings.org, monnier@iro.umontreal.ca, dgutov@yandex.ru To: Juri Linkov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Nov 30 18:37:02 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 1p0R13-000AWh-9H for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 30 Nov 2022 18:37:01 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p0R0w-0000OI-IZ; Wed, 30 Nov 2022 12:36:54 -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 1p0R0l-0000Eb-4B for bug-gnu-emacs@gnu.org; Wed, 30 Nov 2022 12:36:44 -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 1p0R0j-0002kr-Im for bug-gnu-emacs@gnu.org; Wed, 30 Nov 2022 12:36:42 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1p0R05-0007ZM-VR for bug-gnu-emacs@gnu.org; Wed, 30 Nov 2022 12:36:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 30 Nov 2022 17:36:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 56682 X-GNU-PR-Package: emacs Original-Received: via spool by 56682-submit@debbugs.gnu.org id=B56682.166982970929072 (code B ref 56682); Wed, 30 Nov 2022 17:36:01 +0000 Original-Received: (at 56682) by debbugs.gnu.org; 30 Nov 2022 17:35:09 +0000 Original-Received: from localhost ([127.0.0.1]:34066 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1p0QzE-0007Yp-LL for submit@debbugs.gnu.org; Wed, 30 Nov 2022 12:35:08 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:47018) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1p0QzA-0007Xt-Oz for 56682@debbugs.gnu.org; Wed, 30 Nov 2022 12:35:07 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p0Qz4-0002HX-TT; Wed, 30 Nov 2022 12:34:58 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=yTmOxO/AHE3yJrlrZhJ8IEb3NM2R0JFsiBQBHKXLLF8=; b=UA0ch+JKwk4S Ya+gO+MtSWJBU4Ug7RHLpYShX6daeVD5MZAZPxWpF5GIUlOv/60P/XJ6GeIWv83YXAqxi0pblSyqO tCQEWJTKS5+z0v7DLpo7i5Bzn+FyR6OQiNg+fJu7v6Q65rY0gd4wqgxui0XA1noErB1QMll3TGg9A eNPinaYe+1bAv4cs6Zl0f9Bq5HYNtXYAO9HkI42eI2Nikxk5Raz+MBK6nXhpt1ie0/Q0dA0il2gRn STGo7TA9MoEhiiCTeBIRGTbM0V5iutH7m+0cY2QIslAOsT9lZdznPyQFVv3OaXBHF6F86hx9kjLpt tVBNpzp5BC6uPjXZUn3ggg==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p0Qz4-0003Sj-9O; Wed, 30 Nov 2022 12:34:58 -0500 In-Reply-To: <86cz94jxwo.fsf@mail.linkov.net> (message from Juri Linkov on Wed, 30 Nov 2022 18:34:15 +0200) 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:249535 Archived-At: > From: Juri Linkov > Cc: Dmitry Gutov , 56682@debbugs.gnu.org, Eli Zaretskii > , Stefan Monnier > Date: Wed, 30 Nov 2022 18:34:15 +0200 > > 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? 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. > 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? > 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.