From: Alan Mackenzie <acm@muc.de>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] emacs-24 d69e9f1: CC Mode: Stop Font Lock forcing fontification from BOL. Fixes debbugs#19669.
Date: Sat, 7 Feb 2015 15:40:21 +0000 [thread overview]
Message-ID: <20150207154021.GA3764@acm.acm> (raw)
In-Reply-To: <jwv61bdwxie.fsf-monnier+emacsdiffs@gnu.org>
Hello, Stefan.
On Sat, Feb 07, 2015 at 10:29:54AM -0500, Stefan Monnier wrote:
> >> What would be "the closest syntactically safe" position before 409?
> > In the sense meant, 409 is the earliest "syntactically safe" position,
> > since (char-before 409) is "{"
> So, even point-min wouldn't be safe?
No. It has to be somewhere within the enum's braces to work.
> Stefan
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2015-02-07 15:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150201212213.17840.3710@vcs.savannah.gnu.org>
[not found] ` <E1YI1y9-0004eO-Re@vcs.savannah.gnu.org>
2015-02-02 18:50 ` [Emacs-diffs] emacs-24 d69e9f1: CC Mode: Stop Font Lock forcing fontification from BOL. Fixes debbugs#19669 Stefan Monnier
2015-02-02 19:27 ` Alan Mackenzie
2015-02-03 2:12 ` Stefan Monnier
2015-02-02 18:54 ` Stefan Monnier
2015-02-02 21:39 ` Alan Mackenzie
2015-02-03 2:26 ` Stefan Monnier
2015-02-07 12:27 ` Alan Mackenzie
2015-02-07 15:29 ` Stefan Monnier
2015-02-07 15:40 ` Alan Mackenzie [this message]
2015-03-16 23:53 ` Daniel Colascione
2015-03-18 12:08 ` Alan Mackenzie
2015-03-19 3:34 ` Daniel Colascione
2015-03-19 9:31 ` Alan Mackenzie
2015-03-19 13:49 ` Stefan Monnier
2015-03-19 20:37 ` Alan Mackenzie
2015-03-19 20:56 ` Stefan Monnier
2015-03-20 16:30 ` Alan Mackenzie
2015-03-20 16:34 ` Daniel Colascione
2015-03-20 17:29 ` Alan Mackenzie
2015-03-20 21:25 ` Daniel Colascione
2015-03-20 22:30 ` Alan Mackenzie
2015-03-20 18:05 ` Stefan Monnier
2015-03-20 21:12 ` Alan Mackenzie
2015-03-20 22:01 ` Stefan Monnier
2015-03-30 16:44 ` Alan Mackenzie
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=20150207154021.GA3764@acm.acm \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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).