From: martin rudalics <rudalics@gmx.at>
Cc: "Mackenzie, Alan" <AMackenzie@harmanbecker.com>,
emacs-devel@gnu.org, Richard Stallman <rms@gnu.org>,
Alan Mackenzie <acm@muc.de>
Subject: Re: font-locking and open parens in column 0
Date: Sat, 04 Nov 2006 12:35:03 +0100 [thread overview]
Message-ID: <454C7AE7.6070207@gmx.at> (raw)
In-Reply-To: <jwvodro8hy7.fsf-monnier+emacs@gnu.org>
> beginning-of-defun has always been based on regexps and not on syntax, so
> open-paren-in-column-0-is-defun-start in there has no significant impact
> w.r.t. scanning from the beginning of the buffer or not: you can change
> defun-prompt-regexp instead and get the same result.
Does this mean we could use `syntax-ppss' and the car of the 9th field
instead and get rid of `open-paren-in-column-0-is-defun-start' once the
`forward-comment'/`find_defun_start' issue has been resolved? Or,
better, give find_defun_start an additional argument, say "current", to
have it insist on finding the start of the current defun?
> ... and we haven't
> noticeably complexified our parsing technology (contrary to many other
> programming environments).
Once `parse-partial-sexp' is able to handle alternative comment styles
or syntax-table properties (instead of the current text property ersatz)
parsing from bob will get more expensive.
> syntax-ppss is used by font-lock but not only. Whether you could use it for
> the other places where you use your cache? I don't know. I hope so.
> But if you can't I'd be interested to hear about it (mostly to figure out
> in which direction syntax-ppss should be improved).
`syntax-ppss' *is* a major improvement. It lacks a documentation of how
its cache gets filled and a way to customize that.
next prev parent reply other threads:[~2006-11-04 11:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-03 16:19 font-locking and open parens in column 0 Mackenzie, Alan
2006-11-03 19:29 ` Stefan Monnier
2006-11-04 11:35 ` martin rudalics [this message]
2006-11-04 9:30 ` martin rudalics
2006-11-05 7:08 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2006-11-03 8:44 AW: " Mackenzie, Alan
2006-11-03 14:14 ` Stefan Monnier
2006-11-02 8:49 Mackenzie, Alan
2006-11-02 18:31 ` martin rudalics
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=454C7AE7.6070207@gmx.at \
--to=rudalics@gmx.at \
--cc=AMackenzie@harmanbecker.com \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=rms@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).