From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: font-lock-syntactic-keywords obsolet? Date: Mon, 20 Jun 2016 23:32:05 +0300 Message-ID: <18697155-06d3-2191-6a6b-3ea58e8d17cb@yandex.ru> References: <20160619153455.GG5875@acm.fritz.box> <11c988f0-94c0-40dd-b9cd-5a5e27028b63@yandex.ru> <20160619171531.GH5875@acm.fritz.box> <751427e7-f305-7790-99f5-dea230d8e6c4@yandex.ru> <20160620105850.GB3166@acm.fritz.box> <23d7473e-50da-b6dc-17a7-1fec4aad6bfa@yandex.ru> <20160620152535.GB2192@acm.fritz.box> <076b7311-ad16-4913-b0ec-fc73ea4550a1@yandex.ru> <20160620181218.GC2192@acm.fritz.box> <20160620200830.GE2192@acm.fritz.box> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1466457712 401 80.91.229.3 (20 Jun 2016 21:21:52 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 20 Jun 2016 21:21:52 +0000 (UTC) Cc: emacs-devel@gnu.org, Noam Postavsky To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jun 20 23:21:45 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1bF6da-0002lS-QO for ged-emacs-devel@m.gmane.org; Mon, 20 Jun 2016 23:21:42 +0200 Original-Received: from localhost ([::1]:46585 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bF6da-0002Zw-4J for ged-emacs-devel@m.gmane.org; Mon, 20 Jun 2016 17:21:42 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49073) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bF5rg-0005Ky-V3 for emacs-devel@gnu.org; Mon, 20 Jun 2016 16:32:14 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bF5rc-0007dk-O6 for emacs-devel@gnu.org; Mon, 20 Jun 2016 16:32:11 -0400 Original-Received: from mail-lb0-x233.google.com ([2a00:1450:4010:c04::233]:33904) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bF5rc-0007dZ-Fz for emacs-devel@gnu.org; Mon, 20 Jun 2016 16:32:08 -0400 Original-Received: by mail-lb0-x233.google.com with SMTP id oe3so744881lbb.1 for ; Mon, 20 Jun 2016 13:32:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=F5m6wAYFZCkTBywLnWnGS30Y1NEDDbKx7Hu62fx/pK4=; b=nH9b0AMs31xWWJ3l+6DcfRjT3PXsyMzk6r/81LVf1B48mvAak7pM5bEjFTv2E1fl8x Mv0P6MCl1Y9KUeL9+CNiuNIQH2ffXli4uZ2Ed8m0NEaaFBABrwOiPYIFF2BMyl1H9pFW 8XkMaKlfhwYq9GlQv3iS2UI7lNmOY95MUjthvcLfWyy9RBr2IVhaLqk78vviTIbT+Dcg ZNSA/eAa7bCpF4MblmGCCVXobQ83l9MSrinqSd7QU8bUsJxXLxmDIHXuilrjiVff8vZb eHkU5ZiwZWiTwsayhoHpS2YZM8OvqJhvDiFB7iRPPCGG1vzpJvngbIGL3SVDF08bxn80 tOtg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:to:references:cc:from:message-id :date:user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=F5m6wAYFZCkTBywLnWnGS30Y1NEDDbKx7Hu62fx/pK4=; b=UEldRctvxpTfoSqvpio2vz5PyJJTZdizt3whL0Be4GbsMgomgXpR6CR5bI8ZKJVqRo q3BrScakikgINrDHMNXKJDFYPFWQRVPTZZcd/HRpNCjJjCr6SUOfqLqJKzFjGYSY4j9U 7ltW29iAJo7vDRWgUZPOZ27QZnHAWttPhE7093PneKF2zNV8k9RK36awFBd5qeZEji4s gQja+Zq3E+bz2MuJBI9YGPUrnPiWV/fnbAcQKA8xBqKwV+piga7/y4/sofSHZ1H2X7PG gcVICSRHD7fOaRVCviejYHJqGX8cvhl/PEGE9k7MMBIhbNlajSSmfNe/4nyU9Re3lfaM GpCw== X-Gm-Message-State: ALyK8tLSjwDKKURY1Z052R9fd42LRSTi/PT6JwXl7sooqSv3lcMNNLUg5cOY6fZ3h/eilQ== X-Received: by 10.194.141.65 with SMTP id rm1mr16369468wjb.167.1466454727562; Mon, 20 Jun 2016 13:32:07 -0700 (PDT) Original-Received: from [192.168.1.2] ([185.105.173.135]) by smtp.googlemail.com with ESMTPSA id a129sm5216764wma.2.2016.06.20.13.32.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 20 Jun 2016 13:32:06 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2 In-Reply-To: <20160620200830.GE2192@acm.fritz.box> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2a00:1450:4010:c04::233 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:204611 Archived-At: On 06/20/2016 11:08 PM, Alan Mackenzie wrote: > C++ template delimiters (and the like in Java) get parenthesis syntax in > code, but not when in a string. OK, good. Does C++ mode in master support raw strings already? Is there a limit on how far you look for the end of the raw string, and if yes, how much is it? >> Stefan already addressed that: >> http://lists.gnu.org/archive/html/emacs-devel/2016-06/msg00421.html > > He sort of addressed it. The code which implements > syntax-propertize-extend-region-functions is not fully general. For the > general case, you'd need to supplement such a function with a mode > specific before-change function. This is unsubstantiated. > But like he said, normally, you just don't. > > He's wrong. You have, say, in C++ "a < b, c > d", which has been given > s-t properties as a template. You insert "=" after ">". That > necessitates de-propertising the "<" as well as the ">". That's only an issue if `>' is on a different line than `<'. But yes, syntax-propertize-extend-region-functions exist for a reason. > They're handy in the usual case. If by "usual" you just mean the majority of cases you've encountered while using and developing CC Mode. >>> Oh, I'm pretty "educated" about syntax-ppss, thank you very much - >>> educated enough to submit bug reports about it. > >> Just one, and you like reminding us about it every chance you can. > > I'm hoping that, by doing so, it'll get fixed by somebody who isn't me, > given how much I dislike the function. Please do fix it, like you > suggested somewhere else today. You've already expressed dislike for my solution. But sure, I will. > . The meaning we've already established over several posts is > syntax-table text properties whose setting, or lack thereof, is > influenced by arbitrarily distant text in the buffer. You have asserted > that there exist such text properties in Ruby Mode. You still haven't asked a specific question. By now, I've given a thorough enough explanation of how things can go wrong that I have a hard time understanding what kind of example you want. So, again: what question do you want answered? "Tell me something more" is just wasting my time.