From: Roland Winkler <winkler@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 50202@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
Yuu Yin <yuuyin@protonmail.com>
Subject: bug#50202: bibtex-mode: unescaped dollar sign in file field leads to wrong highlighting
Date: Wed, 24 Aug 2022 21:58:25 -0500 [thread overview]
Message-ID: <87zgftqbam.fsf@gnu.org> (raw)
In-Reply-To: <87mtbw4acj.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 22 Aug 2022 16:33:00 +0200")
On Mon, Aug 22 2022, Lars Ingebrigtsen wrote:
> Yuu Yin <yuuyin@protonmail.com> writes:
>
>> - bibtex-mode enabled,
>> - and a BibTeX entry which has as value for file field a path that
>> has dollar sign ~
>> /path/to/file $ name.ext~
>>
>> bibtex-mode doesn't recognizes that the dollar sign is verbatim for
>> the file field, leading to wrong highlighting.
>
> This behaviour is still present in Emacs 29. Perhaps Roland has some
> comments; added to the CCs.
A field "file" is, I believe, not part of standard BibTeX. So the above
is somewhat pushing the limits of BibTeX mode.
From a more practical perspective, I need to say that the above problem
reaches the limits of my knowledge of how font-lock works in general and
how it deals with the (La)TeX delimiter "$" in particular. Occassionally,
unpaired "$" give me strange results in LaTeX documents, though I have
no recipe to illustrate this.
I believe the above problem would require that BibTeX mode first parses
the BibTeX entries. Then it uses different syntax tables for normal
fields and the file field. I do not know how feasable this is, in
particular with larger BibTeX files.
I added Stefan to the CCs. Long time ago, he helped me with font-lock
for BibTeX mode. Maybe he has some comments.
Personally, I use a completely different strategy for associating file
names with BibTeX entries: the BibTeX autokey machinery generates the
nondirectory part of the filename that I associate with an entry. And
find-dired locates the file, whereever it resides under a certain
directory. So there is no file field at all that would require
maintenance.
Roland
next prev parent reply other threads:[~2022-08-25 2:58 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 [this message]
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
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
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=87zgftqbam.fsf@gnu.org \
--to=winkler@gnu.org \
--cc=50202@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--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 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).