From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: master 7362554: Widen around c-font-lock-fontify-region. This fixes bug #38049. Date: Thu, 14 Nov 2019 16:48:17 +0200 Message-ID: <835zjm5xam.fsf@gnu.org> References: <20191109144026.20810.76129@vcs0.savannah.gnu.org> <20191109144027.DDC3720927@vcs0.savannah.gnu.org> <38328d99-23c8-7ba7-a23d-e70ac0aab67a@yandex.ru> <20191111203445.GA5135@ACM> <7497e71d-bab6-fa04-bbc4-f52fadeda16d@yandex.ru> <20191113211936.GB4942@ACM> <6fc930a1-eb47-9e54-8752-8cf7ff041586@yandex.ru> <81e61ed6-27a3-dbdd-34fa-fda779d3e991@yandex.ru> <83blte5y61.fsf@gnu.org> <9eff0b15-b8d0-5340-230e-47eed7cf63cb@yandex.ru> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="67136"; mail-complaints-to="usenet@blaine.gmane.org" Cc: acm@muc.de, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 14 15:48:49 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iVGQS-000HLi-Uo for ged-emacs-devel@m.gmane.org; Thu, 14 Nov 2019 15:48:49 +0100 Original-Received: from localhost ([::1]:58362 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iVGQR-0000eu-Pv for ged-emacs-devel@m.gmane.org; Thu, 14 Nov 2019 09:48:47 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53014) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iVGQI-0000ba-OH for emacs-devel@gnu.org; Thu, 14 Nov 2019 09:48:39 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:52474) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1iVGQH-0005Bv-5a; Thu, 14 Nov 2019 09:48:37 -0500 Original-Received: from [176.228.60.248] (port=2998 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1iVGQE-00063H-0y; Thu, 14 Nov 2019 09:48:35 -0500 In-reply-to: <9eff0b15-b8d0-5340-230e-47eed7cf63cb@yandex.ru> (message from Dmitry Gutov on Thu, 14 Nov 2019 16:35:14 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:242177 Archived-At: > Cc: monnier@iro.umontreal.ca, acm@muc.de, emacs-devel@gnu.org > From: Dmitry Gutov > Date: Thu, 14 Nov 2019 16:35:14 +0200 > > On 14.11.2019 16:29, Eli Zaretskii wrote: > >> From: Dmitry Gutov > >> Date: Thu, 14 Nov 2019 16:05:13 +0200 > >> Cc: Alan Mackenzie , emacs-devel@gnu.org > >> > >> The hope is that calling vertical-motion (or font-lock-ensure directly) > >> inside narrowing is a rare occasion > > > > Why do we need to have such hopes? > > For starters, because it's the current expectation of mmm-mode. :-) It's an unrealistic expectation. Code that narrows a buffer and then invokes something that calls vertical-motion is not special in any case, and could happen anywhere. > > The reality could be different, > > and I'd like us to support those different conditions. It doesn't > > sound like it's much harder. > > There are options, sure. But I think all of them will require explicit > support from major modes. I don't think so. All we need to make sure is that the narrowing doesn't conceal portions of the embedded fragment.