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: feature/improved-locked-narrowing 9dee6df39c: Reworked locked narrowing. Date: Thu, 09 Feb 2023 17:46:24 +0200 Message-ID: <83r0uylu3z.fsf@gnu.org> References: <166939872890.18950.12581667269687468681@vcs2.savannah.gnu.org> <20221125175209.51166C004B6@vcs2.savannah.gnu.org> <6c9d91cffc1bfd801530@heytings.org> <6c9d91cffc394613f58a@heytings.org> <83eds0ksev.fsf@gnu.org> <8aadf0ddd54c85c8144a@heytings.org> <831qnhg3d9.fsf@gnu.org> <9757fbea37611e9c44b9@heytings.org> <83cz6yacxt.fsf@gnu.org> <6943e04e30e5a02a52e6@heytings.org> <838rhk5fy1.fsf@gnu.org> <6943e04e30a40824e107@heytings.org> <83k0143q37.fsf@gnu.org> <94821a0ef100102ac9e0@heytings.org> <83bkmdz04y.fsf@gnu.org> <43562d4dd9dffd81938f@heytings.org> <83357ozhx0.fsf@gnu.org> <83wn4zurit.fsf@gnu.org> <83bkmaueib.fsf@gnu.org> <83357fnwyy.fsf@gnu.org> <83v8kalxsc.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="11911"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 56682@debbugs.gnu.org, monnier@iro.umontreal.ca, akrl@sdf.org To: Gregory Heytings Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Feb 09 16:47:33 2023 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 1pQ993-0002sL-4J for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 09 Feb 2023 16:47:33 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pQ98t-0004XC-9w; Thu, 09 Feb 2023 10:47:23 -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 1pQ98Y-0004L7-FZ for bug-gnu-emacs@gnu.org; Thu, 09 Feb 2023 10:47:03 -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 1pQ98Y-0004lY-77 for bug-gnu-emacs@gnu.org; Thu, 09 Feb 2023 10:47:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pQ98X-0000Os-Nh for bug-gnu-emacs@gnu.org; Thu, 09 Feb 2023 10:47: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: Thu, 09 Feb 2023 15:47: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.16759576181528 (code B ref 56682); Thu, 09 Feb 2023 15:47:01 +0000 Original-Received: (at 56682) by debbugs.gnu.org; 9 Feb 2023 15:46:58 +0000 Original-Received: from localhost ([127.0.0.1]:33310 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pQ98T-0000OZ-Uz for submit@debbugs.gnu.org; Thu, 09 Feb 2023 10:46:58 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:58010) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pQ98Q-0000OK-UQ for 56682@debbugs.gnu.org; Thu, 09 Feb 2023 10:46:56 -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 1pQ98K-0004fj-TM; Thu, 09 Feb 2023 10:46:48 -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=QFs69TzRQspvGoVUclZeRZVGO/Yo6kGhaxk7VFS5/bs=; b=LCrhxlkD/G80 nwo0bj627X0iyY7PU4nx7Q5cM73wRCc7jdiGdPZ4C+Xv78COMAz8+0oHrv5z0UWQaNZ9ggDRY8YIa xVIXncc1a9bvp15Zpl7kwcoiIfLRQqMep0J9i9CGyPjPNthi/xCCZcy5fjew3edYqC2j3xgg5wsyd HlRba0ZPJ7joxBcjPbe+ne+r+6cey4gAYEEvGjKTEuwNtbNzFpfRjjwj3kxKGGUvDN9CnFvihhuif 0g2Et2uKR6E2ogdJiypaYtniDLKBV0CEfo4bwVKeT/2VgaStMh3Jd8sWrqXSiLFL20jsQDe7O8cED uU9MDx1CccMusREaAAO9zg==; 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 1pQ98B-00011v-9D; Thu, 09 Feb 2023 10:46:48 -0500 In-Reply-To: (message from Gregory Heytings on Thu, 09 Feb 2023 14:39:39 +0000) 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:255228 Archived-At: > Date: Thu, 09 Feb 2023 14:39:39 +0000 > From: Gregory Heytings > cc: akrl@sdf.org, monnier@iro.umontreal.ca, 56682@debbugs.gnu.org > > > There's one thing I cannot seem to be able to find in the documentation > > you added: how can a Lisp program know that it is being run under a > > "labeled narrowing", > > A function/macro to check that could indeed be added, its body would be: > > (save-restriction (widen) (buffer-narrowed-p)) We should add it and document it, but I'm surprised that there's no easier way. One problem with the above is that it could cause a more thorough redisplay because it fiddles with buffer restrictions. Also, this doesn't return the label itself. > > and in particular what is the label? Without knowing that, how can Lisp > > programs adapt their behavior to this special kind of narrowing, or even > > just break out of it using without-narrowing? > > That information should be given in the docstring of the function that > creates that narrowing. It is now present in the docstrings of the three > hooks where it is used: Yes, but how do I know which one of these is in effect when my function is called?