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: [Emacs-diffs] scratch/widen-less a4ba846: Replace prog-widen with consolidating widen calls Date: Sat, 02 Dec 2017 19:03:44 -0500 Message-ID: References: <5d668ce5-1482-a3d4-c01b-7d996a532567@yandex.ru> <20171130214621.GA22157@ACM> <27985594-3bb4-ce88-8928-2ccfeac13eae@yandex.ru> <20171201154913.GB3840@ACM> <1e542021-e389-cca4-6acd-349efddb2652@yandex.ru> <20171201223529.GG3840@ACM> <4a94ec5c-efdd-50f1-ff4d-277f5f45c2df@yandex.ru> <20171202202855.GA22133@ACM> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1512259435 15469 195.159.176.226 (3 Dec 2017 00:03:55 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 3 Dec 2017 00:03:55 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: Tom Tromey , Vitalie Spinu , emacs-devel@gnu.org To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Dec 03 01:03:49 2017 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 1eLHl5-0003at-CV for ged-emacs-devel@m.gmane.org; Sun, 03 Dec 2017 01:03:47 +0100 Original-Received: from localhost ([::1]:37302 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eLHlC-0006p0-Ik for ged-emacs-devel@m.gmane.org; Sat, 02 Dec 2017 19:03:54 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35748) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eLHl6-0006ov-Ek for emacs-devel@gnu.org; Sat, 02 Dec 2017 19:03:49 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eLHl3-0005xH-AC for emacs-devel@gnu.org; Sat, 02 Dec 2017 19:03:48 -0500 Original-Received: from pmta11.teksavvy.com ([76.10.157.34]:28024) by eggs.gnu.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.71) (envelope-from ) id 1eLHl3-0005ww-41 for emacs-devel@gnu.org; Sat, 02 Dec 2017 19:03:45 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2GdFQAxPiNa/wx53mhbHQEBBQELAYM8g?= =?us-ascii?q?R81jzqOAgGBfBQgAZhhCoU1BAIChSpEFAEBAQEBAQEBAQNoKEIMAYRVAQQBViM?= =?us-ascii?q?FCwsOJhIUGA0kii0IqheKWAEBAQcCASWDQYh0ixkFkxqPUqELh1yWTYE6NiOBT?= =?us-ascii?q?TIaCDCCZIJRHBmBbCOCXYgKAQEB?= X-IPAS-Result: =?us-ascii?q?A2GdFQAxPiNa/wx53mhbHQEBBQELAYM8gR81jzqOAgGBfBQ?= =?us-ascii?q?gAZhhCoU1BAIChSpEFAEBAQEBAQEBAQNoKEIMAYRVAQQBViMFCwsOJhIUGA0ki?= =?us-ascii?q?i0IqheKWAEBAQcCASWDQYh0ixkFkxqPUqELh1yWTYE6NiOBTTIaCDCCZIJRHBm?= =?us-ascii?q?BbCOCXYgKAQEB?= X-IronPort-AV: E=Sophos;i="5.45,350,1508817600"; d="scan'208";a="11025966" Original-Received: from 104-222-121-12.cpe.teksavvy.com (HELO fmsmemgm.homelinux.net) ([104.222.121.12]) by smtp.teksavvy.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Dec 2017 19:03:44 -0500 Original-Received: by fmsmemgm.homelinux.net (Postfix, from userid 20848) id 1C4AAAE0A9; Sat, 2 Dec 2017 19:03:44 -0500 (EST) In-Reply-To: <20171202202855.GA22133@ACM> (Alan Mackenzie's message of "Sat, 2 Dec 2017 20:28:55 +0000") X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 76.10.157.34 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:220637 Archived-At: > (parse-partial-sexp 1 n) > > . I am proposing extending this property for buffers with several > modes and several syntax tables. Nothing more, nothing less. That would potentially solve some percentage of the problems with MMM support. But what about the rest? > syntax-propertize is your way of doing things, so naturally you want it > to become a "standard". I don't actually care whether the standard is my standard or not. What I wanted was *a* standard. > However it is not the only way of doing things, > and is suboptimal in several respects. All standards are suboptimal. The reason people use them is because the existence of a standard makes other things possible. > When designing syntax-propertize, with whom did you discuss the > technical aspects? My cat. Then I (cause at that point my cat couldn't be bothered to follow me to the desk) tried what we both thought might work, then I applied it to more modes, and a few years later it ends up working in *all* major modes I know (including CC-mode, tho I haven't bothered to make it robust enough to have a patch, knowing that you're never going to accept such a patch in CC-mode, even though it's mostly just throwing away code). Stefan