From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Roland Winkler <winkler@gnu.org>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>,
Lars Ingebrigtsen <larsi@gnus.org>,
48447@debbugs.gnu.org
Subject: bug#48447: 27.2.50; Font-lock error in temporary bibtex-mode buffer
Date: Wed, 13 Jul 2022 16:34:17 -0400 [thread overview]
Message-ID: <jwvy1ww92hd.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87cze83j2a.fsf@gnu.org> (Roland Winkler's message of "Wed, 13 Jul 2022 14:32:13 -0500")
Roland Winkler [2022-07-13 14:32:13] wrote:
> On Wed, Jul 13 2022, Stefan Monnier wrote:
>> Hmm... this looks like a workaround rather than a fix of the core
>> problem because I can't see any use of "font-lock internals" in
>> bibtex.el which would justify such a need.
>>
>> I suspect that the problem is linked to
>> `syntax-propertize-via-font-lock`, so I think the fix should go there.
>
> I am not sure I can follow. Are you saying the proper solution to this
> bug likely needs to go outside bibtex.el but into something like
> syntax-propertize-via-font-lock?
Yup.
> That would put this bug far beyond my emacs hacking skills.
The upside is that it's "not your problem" any more :-)
Stefan
prev parent reply other threads:[~2022-07-13 20:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 17:11 bug#48447: 27.2.50; Font-lock error in temporary bibtex-mode buffer Basil L. Contovounesios
2021-05-18 15:56 ` Roland Winkler
2022-07-13 11:24 ` Lars Ingebrigtsen
2022-07-13 12:32 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-13 12:37 ` Lars Ingebrigtsen
2022-07-13 19:32 ` Roland Winkler
2022-07-13 20:34 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [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
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=jwvy1ww92hd.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=48447@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=winkler@gnu.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 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).