From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: contovob@tcd.ie, 34952@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#34952: files with/out final newline look the same no matter what
Date: Sat, 08 Aug 2020 11:41:30 +0200 [thread overview]
Message-ID: <87mu355vat.fsf@gnus.org> (raw)
In-Reply-To: <jwvwo2ay1yd.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 07 Aug 2020 10:20:50 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> font-lock is "per buffer" whereas point is "per window", so I'm not sure
> what "*the* original point" should mean.
I guess it's not a well-defined question... but some action triggered
the fontification, and I guess what's interesting question here is "what
was point in the window that triggered the fontification"?
> You can try `jit-lock-debug-mode` (which delays the jit-lock from
> "within redisplay" to "the next idle time"). Otherwise, you can set
> `font-lock-support-mode` to nil, then turn font-lock-mode off and back
> on (after which font-lock is triggered via `after-change-functions`).
I see; thanks.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-08-08 9:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-23 5:08 bug#34952: files with/out final newline look the same no matter what 積丹尼 Dan Jacobson
2019-03-23 7:34 ` Eli Zaretskii
2019-03-24 1:07 ` Basil L. Contovounesios
2019-03-24 1:23 ` Basil L. Contovounesios
2020-08-06 19:00 ` Lars Ingebrigtsen
2020-08-07 7:29 ` Lars Ingebrigtsen
2020-08-07 11:07 ` Eli Zaretskii
2020-08-07 11:20 ` Lars Ingebrigtsen
2020-08-07 12:02 ` Lars Ingebrigtsen
2020-08-07 12:11 ` Eli Zaretskii
2020-08-07 12:17 ` Lars Ingebrigtsen
2020-08-07 14:20 ` Stefan Monnier
2020-08-08 9:41 ` Lars Ingebrigtsen [this message]
2020-08-08 13:14 ` Stefan Monnier
2020-08-07 21:54 ` Basil L. Contovounesios
2020-08-08 9:47 ` Lars Ingebrigtsen
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=87mu355vat.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=34952@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=jidanni@jidanni.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).