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: feature/improved-locked-narrowing 9dee6df39c: Reworked locked narrowing. Date: Thu, 09 Feb 2023 14:39:39 +0000 Message-ID: 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> 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="18013"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 56682@debbugs.gnu.org, monnier@iro.umontreal.ca, akrl@sdf.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Feb 09 15:40:28 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 1pQ868-0004XB-6n for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 09 Feb 2023 15:40:28 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pQ85k-0006Cv-J3; Thu, 09 Feb 2023 09:40: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 1pQ85i-0006Ci-OD for bug-gnu-emacs@gnu.org; Thu, 09 Feb 2023 09:40:02 -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 1pQ85i-0007HE-BT for bug-gnu-emacs@gnu.org; Thu, 09 Feb 2023 09:40:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pQ85i-0006F4-3M for bug-gnu-emacs@gnu.org; Thu, 09 Feb 2023 09:40:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Gregory Heytings Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 09 Feb 2023 14:40:02 +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.167595358423961 (code B ref 56682); Thu, 09 Feb 2023 14:40:02 +0000 Original-Received: (at 56682) by debbugs.gnu.org; 9 Feb 2023 14:39:44 +0000 Original-Received: from localhost ([127.0.0.1]:58097 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pQ85P-0006EP-W2 for submit@debbugs.gnu.org; Thu, 09 Feb 2023 09:39:44 -0500 Original-Received: from heytings.org ([95.142.160.155]:49732) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pQ85O-0006EG-Bh for 56682@debbugs.gnu.org; Thu, 09 Feb 2023 09:39:42 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1675953579; bh=PUMN44tQQXbnBYsOCOYqaF26k+0gcUm19liGUs6mQ5A=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=5avj70qGlefyopu3qEi3p9p+BsS45eLhIZyW8ilhsGmpOYLBgivP/bT6DZ1gia4yV 5wm2MEs12D8RfGfwhZeNVSI3PSbCnxu76kwvIDCilOT0oS7Q3qwIr/CAYUpBkwgEh5 9iz5goII9fypjGvCrZc46ZukyDw6OYkpEfr1C251s+tlJ/fWyMPGP2/wHg4yx5If5V 4M9kvO1LOhy7chwv6TV9jyCgmpPnDlREza2X8u+91H7uWf7/VCyuTjkfQeCZ0/EBMC P8ihsr8CpRFiuEpv+ZUXIaFNt+iuXMBlghsVyZ7RnhgEoAX4atLO50Lj23ruumP0eX 3v9cc+lVvqk0g== In-Reply-To: <83v8kalxsc.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:255224 Archived-At: Thanks for your feedback. > > 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)) > > 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: pre-command-hook and post-command-hook: ... these functions are called as if they were in a `with-narrowing' form, with a `long-line-optimizations-in-command-hooks' label ... fontification-functions: ... these functions are called as if they were in a `with-narrowing' form, with a `long-line-optimizations-in-fontification-functions' label ...