From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.bugs Subject: bug#56682: locked narrowing Date: Tue, 18 Oct 2022 19:30:05 +0300 Message-ID: <735c1d5b-0d64-a8e1-3aaa-91fc0248abd3@yandex.ru> 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> <37dd2827f54f8bbda5e3@heytings.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27215"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 Cc: 56682@debbugs.gnu.org, Stefan Monnier To: Gregory Heytings , Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Oct 18 18:51:19 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 1okpoE-0006pi-4Q for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 18 Oct 2022 18:51:18 +0200 Original-Received: from localhost ([::1]:33262 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1okpoC-0006Qp-Uk for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 18 Oct 2022 12:51:17 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40020) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1okpUd-0000XW-8h for bug-gnu-emacs@gnu.org; Tue, 18 Oct 2022 12:31:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:54892) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1okpUc-0001cM-UP for bug-gnu-emacs@gnu.org; Tue, 18 Oct 2022 12:31:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1okpUb-0005cg-PL for bug-gnu-emacs@gnu.org; Tue, 18 Oct 2022 12:31:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Dmitry Gutov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 18 Oct 2022 16:31: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.166611061616522 (code B ref 56682); Tue, 18 Oct 2022 16:31:01 +0000 Original-Received: (at 56682) by debbugs.gnu.org; 18 Oct 2022 16:30:16 +0000 Original-Received: from localhost ([127.0.0.1]:53970 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1okpTs-0004GK-8z for submit@debbugs.gnu.org; Tue, 18 Oct 2022 12:30:16 -0400 Original-Received: from mail-wr1-f52.google.com ([209.85.221.52]:36438) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1okpTo-0003lp-Q1 for 56682@debbugs.gnu.org; Tue, 18 Oct 2022 12:30:14 -0400 Original-Received: by mail-wr1-f52.google.com with SMTP id j7so24499674wrr.3 for <56682@debbugs.gnu.org>; Tue, 18 Oct 2022 09:30:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:content-language:references :cc:to:subject:from:user-agent:mime-version:date:message-id:sender :from:to:cc:subject:date:message-id:reply-to; bh=7VI2DIfYnzonB565gN7X9pQi69WxeQMdhBYGrT6JqEg=; b=a4DKpYLOgFA2VIIMGbcRxZQ/8RsOwOYRuEUyOWfebYY39trxlm3Ma+7s+UeNcYwAcw deyzmzvyw8wnho6gxJXgh9G6nUKAnVQiV3kfw9qkxDGa6AEHai3ukkqS8L8QQjG/JoVH Xcmec/3AcT3nkygCkyl3C3WBtMTb9fZLovwtoB8eRcHte+nwKhvZuTQpqYKIe3SnhB6b enFAG76E5AiRdvN4dcFbH4+6Rys3TVwxkb2Wah8UvGko93CRTumncvn04Oz2RnWDOdec ANrr9rRWKl5pBpcQpEJ6XtPxs2vTATL97v724zkJ2r4flTp+KKEebzgfQL9/nqGY1xtU EYiA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:content-language:references :cc:to:subject:from:user-agent:mime-version:date:message-id:sender :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=7VI2DIfYnzonB565gN7X9pQi69WxeQMdhBYGrT6JqEg=; b=2GOKiyANcngEavlYmTKyjSdq1A+qI48luQMIkaOHtLIC3HufBnoPP1UfPOgahgUdqk 6TDLofjv7NRMxttsdq/zOX8qItjI6ciHWjF4dbl3y6z1NCamD4M3Wqy8IVf9YXe+ZLoB 1muXXdS6M/Ft8EaZMZC9IDDK0RJOyiicG3SNhRbvpu/KJsW182IMqmC7olB8FO5SES0G zdkljvaIl71MEKxqztfMfNWzg5+UyR4DWDItbpZ+y+GMOi4ipkyPfFYo0Ng7modPfud6 T1IcY20K0JkmHCJlPlcPKjFgmlIQeYfDeuZUsvqMj7M1yWo/c6hkrtEkXw5qNWe9MPKT IXjQ== X-Gm-Message-State: ACrzQf3K0qXf77ndbPRlSfbMyRgPkED0WXtOdekRaVxcnLYiMkBGSEzQ 6wiAi2yY/oEXPjE4rbldoG8= X-Google-Smtp-Source: AMsMyM6h3xW9lXuknRZ/bNn7BOqts8UfFsg6bFBSZU2OGLr1z2XZZxNOUhWTTJsU5iYaGb3Z20GJDg== X-Received: by 2002:adf:e442:0:b0:22e:2c5a:721d with SMTP id t2-20020adfe442000000b0022e2c5a721dmr2471689wrm.448.1666110606951; Tue, 18 Oct 2022 09:30:06 -0700 (PDT) Original-Received: from [192.168.0.6] ([46.251.119.176]) by smtp.googlemail.com with ESMTPSA id u14-20020a05600c19ce00b003b477532e66sm3590694wmq.2.2022.10.18.09.30.06 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 18 Oct 2022 09:30:06 -0700 (PDT) Content-Language: en-US In-Reply-To: <37dd2827f54f8bbda5e3@heytings.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:245813 Archived-At: (Sorry, resending after unarchiving the bug) Hi Gregory, I don't mean to hurry you up, but: On 20.08.2022 19:20, Gregory Heytings wrote: > > 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. Does that mean that you concluded that font-lock will be able (and should) unlock the narrowing before doing its thing? Which will be equivalent to not applying the narrowing in handle_fontified_prop to begin with.