From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Noam Postavsky Newsgroups: gmane.emacs.devel Subject: Re: font-lock-syntactic-keywords obsolet? Date: Sun, 19 Jun 2016 09:21:23 -0400 Message-ID: References: <57627D13.5090008@online.de> <5764F25B.4010204@online.de> <20160618171249.GA5796@acm.fritz.box> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1466342496 29405 80.91.229.3 (19 Jun 2016 13:21:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 19 Jun 2016 13:21:36 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jun 19 15:21:36 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 1bEcfQ-0004tP-6g for ged-emacs-devel@m.gmane.org; Sun, 19 Jun 2016 15:21:36 +0200 Original-Received: from localhost ([::1]:38748 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bEcfP-0003cr-AL for ged-emacs-devel@m.gmane.org; Sun, 19 Jun 2016 09:21:35 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50441) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bEcfG-0003ae-H6 for emacs-devel@gnu.org; Sun, 19 Jun 2016 09:21:27 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bEcfE-0000Sm-Hb for emacs-devel@gnu.org; Sun, 19 Jun 2016 09:21:25 -0400 Original-Received: from mail-oi0-x22a.google.com ([2607:f8b0:4003:c06::22a]:35597) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bEcfE-0000Sh-CJ for emacs-devel@gnu.org; Sun, 19 Jun 2016 09:21:24 -0400 Original-Received: by mail-oi0-x22a.google.com with SMTP id a64so23862551oii.2 for ; Sun, 19 Jun 2016 06:21:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-transfer-encoding; bh=vn6a9bPR+RMDhOUg4fWVRALnPAzzS8OcfWLYMf1HlyA=; b=t2vjzqk6fapYyKSRy9sVNQ7Spyy7kpXdP3q/67PdM2yb8E+miE9J+mvLhPGemJTOLy qXpelsOtFQWuIfBjolRluOlx8sBsB7JNmPc2sTp1Rs7RhuW/GdmXiJKlNIKf1bp0KLHt WBPISMDd+WsIcbug0Jk+KtVWab8CyzYelQYDLQOOKyvNakRSYWxs8obFisc+NeJynHpn Jebw1c8yGcFh9Jlh4e87zxslBflivHs8DdHkXmZogwLBNh63oCsiCYXP6+8ptnYhz/B9 ckEIbygY/EPyNh7RdoPWqfRhuYL2iMChMlraC9atr0ivEmCE0gBzXLj14sAVdcICWKtL mQOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:content-transfer-encoding; bh=vn6a9bPR+RMDhOUg4fWVRALnPAzzS8OcfWLYMf1HlyA=; b=gkZhv36l+oVGwp5f+aj8z+syvAaQ41iKsyojjSAgPQxgsQNqlCZujmwF5EJ5ANO0gN iu1f6NiNCC5xWUNWGZTAP+SClxI5MQMJSAqZ+FsD/RwG7DwBW2JVhtDrZQPiOcLazdCI WYZzooByWvDOTyM22ch37g8nYNULdjjZXG/VCtkh4wJSn6cuvY3MzcTyly4m5HmoRYxa eoLtK3Eq6rorNo7l61fQ26wo3cV89GLLNfMlWx+KIL9SUseG43FJtiZybMEz7L7flXu/ R/iRAgzHJSw9GYhzYg+BST49wbGadPYX1SY4wIAwpnOhVj/Qq03xCpDsylbZPTM5a05u kb4g== X-Gm-Message-State: ALyK8tL3/8dBzyivY6+LEOuhQQ7Af6U0kE7faUrMye48pns9gWRNSOp7iLi7lup22aApnNhj6nEQDp1VfsfC6Q== X-Received: by 10.157.1.107 with SMTP id 98mr6573297otu.17.1466342483744; Sun, 19 Jun 2016 06:21:23 -0700 (PDT) Original-Received: by 10.157.52.238 with HTTP; Sun, 19 Jun 2016 06:21:23 -0700 (PDT) In-Reply-To: X-Google-Sender-Auth: aQ-zLmz9ErOBnin8bIPn9ohas04 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:4003:c06::22a 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:204505 Archived-At: On Sun, Jun 19, 2016 at 3:12 AM, Andreas R=C3=B6hler wrote: > The question is if `font-lock-syntactic-keywords' really should be declar= ed > obsolete. > > From docu of `syntax-propertize-function': > > "The specified function may call `syntax-ppss' on any position > before END, but it should not call `syntax-ppss-flush-cache', > which means that it should not call `syntax-ppss' on some > position and later modify the buffer on some earlier position." > > So "on any position" but not "on some position"? > > IMHO that's not ready. > > I'm not sure if you're objecting to the restriction itself, or just the phrasing, e.g. would it be okay like this? "The specified function may call `syntax-ppss' on any position before END, but it should not call `syntax-ppss-flush-cache', meaning that it should not modify the buffer at positions earlier than those on which it called `syntax-ppss'."