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#56682: locked narrowing Date: Fri, 02 Dec 2022 09:14:04 +0000 Message-ID: <20f32a53dc7979bcfb06@heytings.org> References: <837d36ceno.fsf@gnu.org> <37dd2827f54f8bbda5e3@heytings.org> <735c1d5b-0d64-a8e1-3aaa-91fc0248abd3@yandex.ru> <97049541-f5b4-ed3b-b8de-7c0bdc86f0f5@yandex.ru> <6e305c9b-7702-133a-3347-f64db05ade3f@yandex.ru> <83mt89kt10.fsf@gnu.org> <834juglesn.fsf@gnu.org> <83r0xkjw5s.fsf@gnu.org> <83pmd3ioxx.fsf@gnu.org> <47153506021498df087c@heytings.org> <83bkomhlmn.fsf@gnu.org> <4715350602cf2ec6860b@heytings.org> <83a646hkat.fsf@gnu.org> <47153506028bbb3bc8b3@heytings.org> <838rjqgu9b.fsf@gnu.org> <20f32a53dcb7869be445@heytings.org> <83sfhyfas7.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="34315"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 56682@debbugs.gnu.org, monnier@iro.umontreal.ca, dgutov@yandex.ru To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Dec 02 10:15:25 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 1p128i-0008kI-VZ for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 02 Dec 2022 10:15:25 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p128T-00012I-Kp; Fri, 02 Dec 2022 04:15:09 -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 1p128M-00011l-9j for bug-gnu-emacs@gnu.org; Fri, 02 Dec 2022 04:15: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 1p128L-00066E-UZ for bug-gnu-emacs@gnu.org; Fri, 02 Dec 2022 04:15:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1p128L-0004RC-MD for bug-gnu-emacs@gnu.org; Fri, 02 Dec 2022 04:15:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Gregory Heytings Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 02 Dec 2022 09:15: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.166997245217022 (code B ref 56682); Fri, 02 Dec 2022 09:15:01 +0000 Original-Received: (at 56682) by debbugs.gnu.org; 2 Dec 2022 09:14:12 +0000 Original-Received: from localhost ([127.0.0.1]:45510 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1p127X-0004QU-R4 for submit@debbugs.gnu.org; Fri, 02 Dec 2022 04:14:12 -0500 Original-Received: from heytings.org ([95.142.160.155]:40544) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1p127S-0004QN-4O for 56682@debbugs.gnu.org; Fri, 02 Dec 2022 04:14:10 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1669972444; bh=HeW0qAnDNlq/5NmImoS0SWu0Y4ZPmLitzDyP0BlbHhM=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=QfJDfIhKvOGhOqBT+yWPvfI04elsrM7WsqULCyHGXD1KYVeABw1d5YPr5KHTk1v0k suEBp/LWqXrEfl+U/AyuzGHVCPv0+N43z6FfBo66kWNsbnFG48+xscapWjuCsETAn/ /Kg4CpdJj9MYe4SrIoo2LwE3Ez0caox0nQ/OmMYeSUxUqQpwETH0kg6nWZrChpv9m+ Wq9T2btKFmXYSR84lgCp0edQ+GePbFSImvr2O1gHsJ7rr5J8CpKyosJFvNJGLnQmfT uxvHFCEZSpDa46Fwzc0GH5YBkKYwmAkZnRF2Y6IoEuajoeGOBSh/NTf33hQIFFNXye tM5P7xwVYoSrA== In-Reply-To: <83sfhyfas7.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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:249724 Archived-At: >> Stefan's proposed approach looks promising, however. > > I explained why in my other messages why it sounds too complicated. > Yet it's AFAICS the only possible approach that was proposed so far. >> That fix is wrong, sorry. Now the detection loop is triggered each >> time the user changes the narrowing, in the vast majority of cases for >> no good reason. > > The same will happen when the user types several characters. Which > happens more frequently than changes of narrowing, in most use patterns. > The change is wrong nonetheless. It's a local fix to circumvent an example scenario I gave, which was just that: an example. Many other scenarios remain. > > And once again, you simply _cannot_ access buffer text beyond BEGV..ZV > safely. It's a ticking time bomb if you do. > I already said I agree with that. I only said (before Stefan proposed a potential solution) that I did not see a better way to handle that situation. > > I'm sorry, but I cannot afford this endless argument; I'm swamped with > too many tasks that no one else except myself seems to be doing, and > this argument already took an inordinate amount of my time and energy. > > Please install your UNCHANGED_MODIFIED patch, and I will get to > improving the scalability of the scanning loop when I have time. Please > don't install any other changes in this regard except that one patch. > Are you serious??? I mean, I've been spending an inordinate amount of my time to fix that long line problem, I think I now have a certain expertise in that area, I'm trying to find a way to improve these heuristics, you dismiss what I'm telling you, and now you tell me that you have too many tasks on your plate and that you nonetheless want to improve these heuristics yourself and that I should stop working on this???