From: Alan Mackenzie <acm@muc.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: martin rudalics <rudalics@gmx.at>, emacs-devel@gnu.org
Subject: Re: Problems with syntax-ppss
Date: Sun, 6 Apr 2008 14:07:31 +0000 [thread overview]
Message-ID: <20080406140731.GA4084@muc.de> (raw)
In-Reply-To: <jwv63uwxijb.fsf-monnier+emacs@gnu.org>
Hi, Stefan,
On Sat, Apr 05, 2008 at 02:37:39PM -0400, Stefan Monnier wrote:
> >> >I strongly recommend to always call syntax-ppss in a widened
> >> >buffer.
> >> ... and with match-data saved.
> > Er, your replies don't exactly radiate an aura of confidence about
> > syntax-ppss. ;-(
> > I think you (Stefan) 're saying that the function isn't 100% defined
> > for a narrowed buffer.
> Indeed.
That's not good.
> > Will calling s-ppss on a narrowed buffer corrupt the cache at all,
> > for example?
> Yes it can. Similarly the cache does not keep track of the
> syntax-table so if you switch syntax-table between calls you may get
> unexpected results.
That's also not good.
Would it not be a good idea to (i) redefine syntax-ppss as calculating
the syntax from BOB (as opposed to (point-min)); (ii) have several
caches, each associated with a particular syntax table (how many modes
are going to use more than 2 or, perhaps, 3?); (iii) put a
`save-match-data' round the function?
[ Stuff about performance read and appreciated. ]
> Stefan
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2008-04-06 14:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 17:26 Problems with syntax-ppss Alan Mackenzie
2008-04-04 17:29 ` Lennart Borgman (gmail)
2008-04-04 20:24 ` Stefan Monnier
2008-04-04 21:14 ` martin rudalics
2008-04-05 14:46 ` Alan Mackenzie
2008-04-05 18:37 ` Stefan Monnier
2008-04-06 14:07 ` Alan Mackenzie [this message]
2008-04-07 14:57 ` Stefan Monnier
2008-04-07 15:14 ` Lennart Borgman (gmail)
2008-04-07 16:43 ` Stefan Monnier
2008-04-07 14:59 ` Stefan Monnier
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=20080406140731.GA4084@muc.de \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rudalics@gmx.at \
/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).