all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: "Wedler, Christoph" <christoph.wedler@sap.com>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Clarification needed: syntax-propertize vs font-lock-syntax-table
Date: Tue, 24 Nov 2015 13:35:04 +0200	[thread overview]
Message-ID: <56544B68.90204@yandex.ru> (raw)
In-Reply-To: <F9C2521BBF380A4A97379009991555E6993579ED@DEWDFEMB17C.global.corp.sap>

On 11/24/2015 10:58 AM, Wedler, Christoph wrote:

> I now checked the code: it is done via jit-lock-after-change in
> after-change-functions.  As I have guessed, syntax-propertize currently
> only works correctly if font-lock is switched on.

font-lock depends on syntax-propertize. Not the other way around.

> Yes, but navigation command like M-x forward-list do not depend on
> font-lock, but they do depend on syntax-propertize (consider parentheses
> in generic strings).

Hm, actually, that has changed in 
ab21f61a552f038485d40218dfd94a16b843eb52. So yes, there's a difference 
between Emacs 24 and 25 here. Sorry for the confusion.

> Ok, I'll name it syntax-ppss-open-positions (like (nth 0 ppss) is called
> syntax-ppss-depth, and not syntax-ppss-list-depth).

Sounds good.

> Well, that was the point of the above function: in the former case, the
> function body is changed to (mapcar 'car (nth 9 ppss)), and will stay
> the same in the latter.

Sorry, I lost you here. Former case?



      reply	other threads:[~2015-11-24 11:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-18 18:06 Clarification needed: syntax-propertize vs font-lock-syntax-table Wedler, Christoph
2015-11-18 18:37 ` Dmitry Gutov
2015-11-20 18:24   ` Wedler, Christoph
2015-11-20 18:39     ` Dmitry Gutov
2015-11-23 17:05       ` Wedler, Christoph
2015-11-23 19:01         ` Dmitry Gutov
2015-11-24  8:58           ` Wedler, Christoph
2015-11-24 11:35             ` Dmitry Gutov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56544B68.90204@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=christoph.wedler@sap.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.