From: "Roland Winkler" <winkler@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 21099@debbugs.gnu.org, Brian Zbriger <brian.zbr@gmail.com>,
Gustavo Barros <gusbrs.2016@gmail.com>
Subject: bug#21099: 24.3; bibtex-clean-entry and date fields in biblatex
Date: Sun, 4 Aug 2019 14:48:00 -0500 [thread overview]
Message-ID: <13936.24188.845267.23879@gargle.gargle.HOWL> (raw)
In-Reply-To: <87blx7phf7.fsf@mouse.gnus.org>
On Fri Aug 2 2019 Lars Ingebrigtsen wrote:
> Gustavo Barros <gusbrs.2016@gmail.com> writes:
>
> > So, with defaults, from an original entry like:
> >
> > @Article{Author2019c,
> > author = {Author},
> > title = {Title},
> > journaltitle = {Journal title},
> > date = {2019},
> > }
> >
> > the result of `bibtex-clean-entry` is:
> >
> > @Article{Author2019c,
> > author = {Author},
> > title = {Title},
> > journaltitle = {Journal title},
> > date = 2019,
> > }
>
> Right; this is what the bug report claims makes latexmk and biber stop
> working, but you say later that this isn't the case? Could there be
> versions of these programs that choke on brace-less entries?
If for whatever reason you do not want to remove the braces from a
numeric field such as `date', you can achieve this by removing the
element numerical-fields from the user variable bibtex-entry-format.
(The element numerical-fields has been part of the default value of
bibtex-entry-format for longer than I have been the maintainer of
bibtex.el (since ~1999).)
prev parent reply other threads:[~2019-08-04 19:48 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
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 [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=13936.24188.845267.23879@gargle.gargle.HOWL \
--to=winkler@gnu.org \
--cc=21099@debbugs.gnu.org \
--cc=brian.zbr@gmail.com \
--cc=gusbrs.2016@gmail.com \
--cc=larsi@gnus.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 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.