From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: forward-comment and syntax-ppss Date: Sat, 17 Dec 2016 09:41:18 -0500 Message-ID: References: <83fd1db0-7362-6117-c5cd-715398c0dea4@gmail.com> <20161207220447.GA4503@acm.fritz.box> <20161208201517.GB3120@acm.fritz.box> <20161209190747.GC2203@acm.fritz.box> <5a70902f-882e-f616-74b2-df6eb81fc70c@yandex.ru> <20161211101715.GA14084@acm.fritz.box> <51c0554f-40d0-37a5-b134-17058343aa3f@yandex.ru> <20161216200630.GB3858@acm.fritz.box> <83r3576lxs.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1481985693 27524 195.159.176.226 (17 Dec 2016 14:41:33 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 17 Dec 2016 14:41:33 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) Cc: acm@muc.de, emacs-devel@gnu.org, dgutov@yandex.ru To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Dec 17 15:41:29 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cIGAw-0005x8-8J for ged-emacs-devel@m.gmane.org; Sat, 17 Dec 2016 15:41:26 +0100 Original-Received: from localhost ([::1]:36921 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cIGB0-0002tI-Kj for ged-emacs-devel@m.gmane.org; Sat, 17 Dec 2016 09:41:30 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38798) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cIGAu-0002sw-9Q for emacs-devel@gnu.org; Sat, 17 Dec 2016 09:41:25 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cIGAt-0008FM-BV for emacs-devel@gnu.org; Sat, 17 Dec 2016 09:41:24 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:49360) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cIGAp-0008Bt-Iu; Sat, 17 Dec 2016 09:41:19 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0BXNQAu3EVY/+J3oWxdGgEBAQECAQEBAQgBAQEBgyoOAQEBAQEfhFuFVJwCJgGUVoIIhhwEAgKCEUISAQIBAQEBAQEBYihCEgGEFAEEAVYjEAs0EhQYDSSIegitFItEAQEBBwIBJIsZiikFj3yKIkibGoY6kE6BQSYDLXgTDoVzIIYxgnwBAQE X-IPAS-Result: A0BXNQAu3EVY/+J3oWxdGgEBAQECAQEBAQgBAQEBgyoOAQEBAQEfhFuFVJwCJgGUVoIIhhwEAgKCEUISAQIBAQEBAQEBYihCEgGEFAEEAVYjEAs0EhQYDSSIegitFItEAQEBBwIBJIsZiikFj3yKIkibGoY6kE6BQSYDLXgTDoVzIIYxgnwBAQE X-IronPort-AV: E=Sophos;i="5.33,749,1477972800"; d="scan'208";a="282975141" Original-Received: from 108-161-119-226.dsl.teksavvy.com (HELO pastel.home) ([108.161.119.226]) by smtp.teksavvy.com with ESMTP; 17 Dec 2016 09:41:18 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 6C4DB64B6A; Sat, 17 Dec 2016 09:41:18 -0500 (EST) In-Reply-To: <83r3576lxs.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 17 Dec 2016 09:42:39 +0200") X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.181 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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:210582 Archived-At: >> > The idea is to move the user-facing narrowing commands to some other >> > foundation (like the invisible and maybe intangible text properties), >> > freeing the narrowing facility for use by the Lisp code. >> While it might be a good direction, it's not as simple as it sounds, >> since many uses of the C-x n n command looks like "narrow to the region, >> and then apply to the whole buffer": I think it will be tricky >> to make overlays that mimick this behavior sufficiently well. > Do you have an alternative proposal? Yes, I think it's easier to keep using narrow-to-region for that, but to supplement the narrowing with some information as to whether widening that narrowing is permissible or not (along the lines of font-lock-dont-widen, but not specific to font-lock and allowing intermediate narrowing so that we can widen the user's narrowing in an Info buffer without widening all the way to point-min==1). Stefan