From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: font-lock-syntactic-keywords obsolet? Date: Sun, 19 Jun 2016 22:58:44 -0400 Message-ID: References: <57627D13.5090008@online.de> <5764F25B.4010204@online.de> <20160618171249.GA5796@acm.fritz.box> <20160619151227.GD5875@acm.fritz.box> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1466391604 26863 80.91.229.3 (20 Jun 2016 03:00:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 20 Jun 2016 03:00:04 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jun 20 04:59:51 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 1bEpRH-0003La-9y for ged-emacs-devel@m.gmane.org; Mon, 20 Jun 2016 04:59:51 +0200 Original-Received: from localhost ([::1]:40949 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bEpRG-00078U-G2 for ged-emacs-devel@m.gmane.org; Sun, 19 Jun 2016 22:59:50 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33788) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bEpQU-00076h-QQ for emacs-devel@gnu.org; Sun, 19 Jun 2016 22:59:03 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bEpQQ-0003UP-NJ for emacs-devel@gnu.org; Sun, 19 Jun 2016 22:59:01 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:50668) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bEpQQ-0003UG-Fp for emacs-devel@gnu.org; Sun, 19 Jun 2016 22:58:58 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1bEpQM-0002ci-8i for emacs-devel@gnu.org; Mon, 20 Jun 2016 04:58:54 +0200 Original-Received: from 45.72.244.67 ([45.72.244.67]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 20 Jun 2016 04:58:54 +0200 Original-Received: from monnier by 45.72.244.67 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 20 Jun 2016 04:58:54 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 30 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 45.72.244.67 User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) Cancel-Lock: sha1:3oQ9JAKbK89yDJQfk3Q7RL1PEK4= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 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:204560 Archived-At: >> > The question is if `font-lock-syntactic-keywords' really should be >> > declared obsolete. [...] >> That presumes that font-lock-syntactic-keywords does not suffer from >> tricky interactions with syntax-ppss. Of course, that's not the case, >> instead these are simply undocumented. [...] > Wouldn't the answer be simply to document these? The answer to what? To the question of whether `font-lock-syntactic-keywords' should be declared obsolete? Well, I guess you're right that it would make it slightly more obvious why it should be declared obsolete, but frankly, I don't care that much if people understand why. It just has been declared obsolete and if you want that decision to be reverted you should provide good arguments against it. "syntax-propertize is not perfect" is clearly not a good enough argument, especially when the imperfections hinted at (Andreas Röhler still hasn't revealed what he considers are those imperfections) also affect `font-lock-syntactic-keywords'. If someones doesn't like something about syntax-propertize (or syntax-ppss), they should file a bug report. And if they want that thing to be improved, providing a good concrete case where the misfeature bites is always a good way to motivate people to fix it. E.g. the caveat regarding the use of syntax-ppss from syntax-propertize could be fixed if it's important enough (I don't think there's anything particularly hard about it). Stefan