From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: 8626@debbugs.gnu.org
Subject: bug#8626: 24.0.50; (elisp) Region to Fontify after a Buffer Change - Why a child of Multiline Font Lock?
Date: Fri, 6 May 2011 08:00:50 -0700 [thread overview]
Message-ID: <86CA0AD6E28C4F9687E6B9F09D00218B@us.oracle.com> (raw)
In-Reply-To: <jwvpqnv28ov.fsf-monnier+emacs@gnu.org>
> > What limits the import of this node to multiline font-lock?
> > Nothing that I can see.
>
> Maybe the problem is "your" notion of "multiline font-lock"?
>
> There's no such thing as a "multiline font-lock" feature or
> functionality, but only "Multiline Font Lock Constructs",
> i.e. there are cases where a major mode needs to get font-lock
> to recognize elements that span multiple lines.
That _is_ "my" notion of "multiline font-lock" (and that's your term, not mine).
> > This node is about refontification after buffer changes. It is not,
> > logically, a subnode of `Multiline Font Lock Constructs'.
>
> It is about having to extend the refontification area because
> refontifying a single-line is not sufficient, presumably because the
> major mode has to handle a multiline font-lock construct.
The node _says_ it is about what you say up to the comma. You then add
"presumably...", which is _not_ part of the node content. This info is missing.
Also missing is whether anything stronger than "presumably" applies.
The node content is about the region to refontify after a buffer change. It
mentions that in some cases code might need to extend that region, to DTRT.
That's all that is said.
If the _only_ time this is pertinent is in the context of multiline font-lock
constructs, then please say so (and perhaps why, if helpful). If it is not the
only time, then add that this _can_ happen, in particular, in the context of
multiline font-lock constructs.
You seem to be fighting making this text clear. Please clearly specify how and
how much the (current) node content is related to multiline font-lock
constructs. That's what is missing.
next prev parent reply other threads:[~2011-05-06 15:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 22:21 bug#8626: 24.0.50; (elisp) Region to Fontify after a Buffer Change - Why a child of Multiline Font Lock? Drew Adams
2011-05-06 13:46 ` Stefan Monnier
2011-05-06 14:01 ` Drew Adams
2011-05-06 14:46 ` Stefan Monnier
2011-05-06 15:00 ` Drew Adams [this message]
2011-05-06 17:20 ` Stefan Monnier
2011-07-15 13:24 ` Lars Magne Ingebrigtsen
2011-07-15 14:30 ` Drew Adams
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=86CA0AD6E28C4F9687E6B9F09D00218B@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=8626@debbugs.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 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.