From: Lars Ingebrigtsen <larsi@gnus.org>
To: Gustavo Barros <gusbrs.2016@gmail.com>
Cc: Brian Zbriger <brian.zbr@gmail.com>, 21099@debbugs.gnu.org
Subject: bug#21099: 24.3; bibtex-clean-entry and date fields in biblatex
Date: Fri, 02 Aug 2019 13:22:50 +0200 [thread overview]
Message-ID: <87wofv95h1.fsf@mouse.gnus.org> (raw)
In-Reply-To: <8736ik61l6.fsf@gmail.com> (Gustavo Barros's message of "Thu, 01 Aug 2019 18:02:45 -0300")
Gustavo Barros <gusbrs.2016@gmail.com> writes:
> I can add two things about this. First, that I’ve been using
> bibtex-mode for some time, with `(bibtex-dialect (quote biblatex))` and,
> with proper configuration of `bibtex-entry-format`, namely the exclusion
> of value `numerical-fields` which is added by default, I get braces in
> all of my fields, including date/year ones when using
> `bibtex-clean-entry`.
Do you have an example bibtex file that demonstrates the error in
`bibtex-clean-entry'?
> On the other hand, it is true there is a dearth of documentation for
> "bibtex.el". It’s comments state:
>
>> See documentation for `bibtex-mode' or type "M-x describe-mode" when
>> you are in BibTeX mode.
>
> I might have missed it, but I cannot find a built-in documentation for
> it. And what we get for "C-h m" is scant.
`C-h f bibtex-mode RET' gives me a quite long doc string (in Emacs 27,
at least).
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-08-02 11:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 3:16 bug#21099: 24.3; bibtex-clean-entry and date fields in biblatex Brian Zbriger
2019-08-01 20:23 ` Lars Ingebrigtsen
2019-08-01 21:02 ` Gustavo Barros
2019-08-02 11:22 ` Lars Ingebrigtsen [this message]
2019-08-02 13:30 ` Gustavo Barros
2019-08-02 18:10 ` Lars Ingebrigtsen
2019-08-02 19:18 ` Gustavo Barros
2019-08-02 20:52 ` Gustavo Barros
2019-08-03 12:18 ` Lars Ingebrigtsen
2019-08-04 19:48 ` 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=87wofv95h1.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=21099@debbugs.gnu.org \
--cc=brian.zbr@gmail.com \
--cc=gusbrs.2016@gmail.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.