From: rfflrccrd@gmail.com
To: help-gnu-emacs@gnu.org
Subject: Re: font-lock-keywords: matcher function not working
Date: Fri, 28 Jun 2013 03:43:05 -0700 (PDT) [thread overview]
Message-ID: <8d3f8211-d708-4e79-aab4-6cc8141c6c92@googlegroups.com> (raw)
In-Reply-To: <mailman.2602.1372354403.22516.help-gnu-emacs@gnu.org>
On Thursday, June 27, 2013 7:32:57 PM UTC+2, Stefan Monnier wrote:
> Your rr-match-indented-paren should *search* rather than only check the
>
> current position.
Thank you for your attention, Stefan.
However, doesn't my matcher function search already? It checks the
current position first to return NIL for a failed match. OTOH, when
the check succeeds, the matcher function calls `re-search-forward' to
set `match-data' appropriately. IMO, this is the expected behaviour
according to the documentation of `font-lock-keywords':
"MATCHER [...] should return non-nil, move point, and set `match-data'
appropriately if it succeeds; like `re-search-forward' would."
Otherwise - that is: when the match fails - MATCHER should do nothing
and return NIL, shouldn't it?
> While I'm here, I recommend you (setq font-lock-support-mode nil) then
>
> disable&enable font-lock so that jit-lock won't be used: this makes it
>
> much easier to debug the code, especially when it signals errors (or
>
> course, you also want to set debug-on-error to t).
Thank you for these tips.
next prev parent reply other threads:[~2013-06-28 10:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 12:39 font-lock-keywords: matcher function not working Raffaele Ricciardi
2013-06-27 12:40 ` Raffaele Ricciardi
2013-06-27 17:32 ` Stefan Monnier
[not found] ` <mailman.2602.1372354403.22516.help-gnu-emacs@gnu.org>
2013-06-28 10:43 ` rfflrccrd [this message]
2013-06-28 19:30 ` Stefan Monnier
[not found] ` <mailman.2731.1372447819.22516.help-gnu-emacs@gnu.org>
2013-06-28 20:50 ` Raffaele Ricciardi
2013-06-29 2:35 ` Stefan Monnier
[not found] ` <mailman.2762.1372473348.22516.help-gnu-emacs@gnu.org>
2013-06-29 8:53 ` Raffaele Ricciardi
2013-06-29 13:32 ` Raffaele Ricciardi
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=8d3f8211-d708-4e79-aab4-6cc8141c6c92@googlegroups.com \
--to=rfflrccrd@gmail.com \
--cc=help-gnu-emacs@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.