[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: font-lock-syntactic-keywords obsolet?

From: Andreas Röhler
Subject: Re: font-lock-syntactic-keywords obsolet?
Date: Sun, 19 Jun 2016 16:03:46 +0200
User-agent: Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Icedove/45.1.0

On 19.06.2016 15:21, Noam Postavsky wrote:
On Sun, Jun 19, 2016 at 3:12 AM, Andreas Röhler
<address@hidden> wrote:
The question is if `font-lock-syntactic-keywords' really should be declared

 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'."

If some specific keywords should be fontified, what has `syntax-ppss' here to interfere at all?

`font-lock-syntactic-keywords' is documented as
  "A list of the syntactic keywords to put syntax properties on.

which is straightforward. Defining resp. changing these keywords is well introduced all what's needed in many cases. Users are free to specify, what a syntactic keyword should be.

Let's look in contrast to proposed replacement:

"Mode-specific function to apply `syntax-table' text properties."

Aren't specifying keywords and function, which applies a syntax-table different things?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]