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: Sat, 20 Aug 2022 16:20:57 +0000 Message-ID: <37dd2827f54f8bbda5e3@heytings.org> References: <831qtgff78.fsf@gnu.org> <83zgg4dw4y.fsf@gnu.org> <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> 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="35276"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 56682@debbugs.gnu.org, Stefan Monnier , dgutov@yandex.ru To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Aug 20 18:21:15 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 1oPRDn-0008wY-Bk for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 20 Aug 2022 18:21:15 +0200 Original-Received: from localhost ([::1]:59508 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oPRDl-0007H0-CK for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 20 Aug 2022 12:21:13 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49282) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oPRDb-0007Gr-Ji for bug-gnu-emacs@gnu.org; Sat, 20 Aug 2022 12:21:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:43664) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oPRDb-0002YH-6s for bug-gnu-emacs@gnu.org; Sat, 20 Aug 2022 12:21:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oPRDa-0004Dc-Hf for bug-gnu-emacs@gnu.org; Sat, 20 Aug 2022 12:21:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Gregory Heytings Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 20 Aug 2022 16:21: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.166101246116190 (code B ref 56682); Sat, 20 Aug 2022 16:21:02 +0000 Original-Received: (at 56682) by debbugs.gnu.org; 20 Aug 2022 16:21:01 +0000 Original-Received: from localhost ([127.0.0.1]:33413 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oPRDZ-0004D2-8a for submit@debbugs.gnu.org; Sat, 20 Aug 2022 12:21:01 -0400 Original-Received: from heytings.org ([95.142.160.155]:33132) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oPRDW-0004Ct-Qa for 56682@debbugs.gnu.org; Sat, 20 Aug 2022 12:21:00 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1661012457; bh=t+nXdKcsrSp082ZwmjfEZQ4JAMJErk9Rw4cGvBG05FU=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=Cw5j3t4ZVhekJO1dGV7cODQARxH1Ttw7ZdhrKj5pyhlJ5zOGlRBCjotx0yvz5gUlW oXWyVcAK4y7/19G6FWEICve/W9JPis0lG5jbaLJhUMCLmuMX7NzZdkdNsuOlLeDhi3 twiPZTt1l+iuSGfYkuVaNeHNiRabU2Rb8wM1KOVEXmMIKB74Fh7WajZEpUPNvszE79 PylDz2OKGnDqYa0TxquoPubVEwtYUkl7w9qnYDpUYqqEF++Ng3LGKoeyMNi7RAwr87 ldKuWnilvouJv1yTD15b/eO+60OM5dJQVfoEBOnQ+tkFmwRFK859MNka+cF5s3CXMj yFh7JInZ8jruQ== In-Reply-To: <837d36ceno.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" Xref: news.gmane.io gmane.emacs.bugs:240257 Archived-At: I pushed a (hopefully) improved version of the the locked narrowing feature in the feature/improved-locked-narrowing branch. It is now possible: 1. to unlock a locked narrowing, 2. to use narrow-to-region and widen within the bounds of a locked narrowing, 3. to enter and leave a locked narrowing within a locked narrowing, and 4. to use that feature in Lisp code (either directly or with a helper macro). As far as I understand, given that it is possible to unlock a locked narrowing, adding the possibility to choose how the bounds of the locked narrowings are computed has become unnecessary. Comments/feedback welcome.