From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
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: Fri, 07 Aug 2020 14:02:31 +0200 [thread overview]
Message-ID: <87wo2a7jfs.fsf@gnus.org> (raw)
In-Reply-To: <87imdu8zxm.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 07 Aug 2020 13:20:53 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Oh, yeah, that makes sense. I'll fix that.
Actually, I don't know how. How do you ask, when you're in the
font-lock machinery, what the original point was? Like here:
,@(when (memq 'missing-newline-at-eof whitespace-active-style)
;; Show missing newline.
`(("[^\n]\\'" 0 (if .... something) t)))))
By the way, have I whined about how difficult debugging font-lock stuff
is? I can't put a `debug' in there, for instance, to examine the
calling sequence, which would probably tell me what I need to know.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-08-07 12:02 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wo2a7jfs.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=34952@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=eliz@gnu.org \
--cc=jidanni@jidanni.org \
/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.