From: "Drew Adams" <drew.adams@oracle.com>
To: "'Lars Magne Ingebrigtsen'" <larsi@gnus.org>,
"'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, 15 Jul 2011 07:30:35 -0700 [thread overview]
Message-ID: <E2F8BBD6C755451BA612390CF67BD8B5@us.oracle.com> (raw)
In-Reply-To: <m3r55rad7c.fsf@quimbies.gnus.org>
If you dropped into this node from elsewhere than it parent, you would see
nothing about multiline font-lock constucts. (And even coming from that node
you will see nothing about them.)
You would learn about refontifying the region after a buffer change, in
particular that in some cases refontifying needs to extend the region. That's
all.
No one has yet answered the question that would unambiguously tie this to
multiline font-lock constructs: is this region extension for refontifying
pertinent _ONLY_ in the context of multi-line font-lock constructs? As I 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.
Answer that question for readers and you've fixed this bug.
prev parent reply other threads:[~2011-07-15 14:30 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
2011-05-06 17:20 ` Stefan Monnier
2011-07-15 13:24 ` Lars Magne Ingebrigtsen
2011-07-15 14:30 ` Drew Adams [this message]
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=E2F8BBD6C755451BA612390CF67BD8B5@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=8626@debbugs.gnu.org \
--cc=larsi@gnus.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.