From: Edgar Lux <edgarlux@mailfence.com>
To: help-gnu-emacs@gnu.org
Subject: Feature request: better biber (comment) support
Date: Fri, 30 Jun 2023 16:08:57 +0200 (CEST) [thread overview]
Message-ID: <1962536429.113839.1688134137797@ichabod.co-bxl> (raw)
Hi! As I was inserting a cite with org-cite, I realised that it was checking the validity of my .bib file. I am using BibLaTeX (biber), and I had some entries with comments starting with %. =bibtex-validate= disproves such lines, but even @COMMENT does not seem to work on them. I resorted to using comment = {...}. May be it would be important to update the code to support biber (BibLaTeX) as well; may be there is work in a newer version of Emacs.
references:
- https://tex.stackexchange.com/questions/325696/code-comments-in-a-biblatex-file
- https://tex.stackexchange.com/questions/21709/comments-in-bibtex
- https://tex.stackexchange.com/questions/93972/comment-out-sections-of-text-in-bib-file
Emacs 28.2 on GNU Linux (is there something else? ;) )
Thanks!
--
Sent with https://mailfence.com
Secure and private email
reply other threads:[~2023-06-30 14:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1962536429.113839.1688134137797@ichabod.co-bxl \
--to=edgarlux@mailfence.com \
--cc=help-gnu-emacs@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.
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).