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: Lars Ingebrigtsen <larsi@gnus.org>,
50202@debbugs.gnu.org, Yuu Yin <yuuyin@protonmail.com>
Subject: bug#50202: bibtex-mode: unescaped dollar sign in file field leads to wrong highlighting
Date: Fri, 26 Aug 2022 15:00:31 -0400 [thread overview]
Message-ID: <jwvbks625rn.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87r113knmw.fsf@gnu.org> (Roland Winkler's message of "Fri, 26 Aug 2022 10:52:55 -0500")
> For me, the situation is opposite: in my BibTeX files (with quite many
> entries that have accumulated over the years), many entries contain
> LaTeX constructs like $^2$ so that I appreciate proper highlighting.
> But I never encountered the opposite problem when a field should contain
> a single $.
My BibTeX file is in the same boat as yours, but I don't find the
highlighting of those thingies important at all. The $ signs themselves
are more than enough to clarify visually what is what, since the text
between them is invariably short.
>> The other option is to try and make this choice on a field-by-field
>> basis, which seems like a lot of work for fairly little benefit.
>
> I agree it doesn't make sense to (try to) highlight different fields
> differently. That's why I suggest that bibtex-mode continues to use
> only one syntax table. But make it customizable how this syntax table
> treats $: You and the OP can make it a punctuation character (also fine
> with me as default, it doesn't cause harm), while it remains possible to
> keep the current behavior.
Another option is to mark $ as punctuation and then rely instead on
`font-lock-keywords` to highlight something like "\\$[^$\n]+\\$".
So $^2$ would still be highlighted in URLs but "foo$bar" wouldn't.
Stefan
next prev parent reply other threads:[~2022-08-26 19:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 17:48 bug#50202: bibtex-mode: unescaped dollar sign in file field leads to wrong highlighting Yuu Yin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-22 14:33 ` Lars Ingebrigtsen
2022-08-25 2:58 ` Roland Winkler
2022-08-25 12:52 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-25 16:36 ` Roland Winkler
2022-08-25 17:41 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-26 15:52 ` Roland Winkler
2022-08-26 19:00 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-08-29 15:19 ` Roland Winkler
2022-12-30 5:49 ` Roland Winkler
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=jwvbks625rn.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=50202@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=winkler@gnu.org \
--cc=yuuyin@protonmail.com \
/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.