[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: XKCD/541 compliance, anyone?
From: |
Stefan Monnier |
Subject: |
Re: XKCD/541 compliance, anyone? |
Date: |
Fri, 02 Jan 2015 20:49:30 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (gnu/linux) |
> Do I get it correctly that it "outputs" a function, so that I can
> write
> (setq syntax-propertize-function (syntax-propertize-rules (...)))
> ?
That's right.
> I have global font lock mode, so font locking is on everywhere.
Nope: global-font-lock-mode only enabled font-lock in those modes where
there are font-lock keywords defined.
>>> but then again, not in message mode, for instance.
>> Probably because font-lock-keywords-only is set to t, so font-lock
>> doesn't end up calling syntax-ppss.
> Now that is strange: it seems that font-lock-keywords-only is set to t
> in mu4e-message mode (where I'm now), but grepping through mu4e sources
> didn't give any results (nor did isearching message.el). I'll have to
> look into this further (check other modes etc.)
That's because font-lock-keywords-only is set indirectly via the 2nd
element of `font-lock-defaults'.
Stefan
Re: XKCD/541 compliance, anyone?, Marcin Borkowski, 2015/01/02
- Re: XKCD/541 compliance, anyone?,
Stefan Monnier <=
Re: XKCD/541 compliance, anyone?, Marcin Borkowski, 2015/01/07
- Re: XKCD/541 compliance, anyone?, Stefan Monnier, 2015/01/07
- Re: XKCD/541 compliance, anyone?, Marcin Borkowski, 2015/01/07
- Re: XKCD/541 compliance, anyone?, Stefan Monnier, 2015/01/07
- Re: XKCD/541 compliance, anyone?, Marcin Borkowski, 2015/01/07
- Message not available
- Re: XKCD/541 compliance, anyone?, Stefan Monnier, 2015/01/07
- Re: XKCD/541 compliance, anyone?, Marcin Borkowski, 2015/01/08