unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Gustavo Barros <gusbrs.2016@gmail.com>
Cc: 21099@debbugs.gnu.org, Brian Zbriger <brian.zbr@gmail.com>,
	Roland Winkler <winkler@gnu.org>
Subject: bug#21099: 24.3; bibtex-clean-entry and date fields in biblatex
Date: Fri, 02 Aug 2019 20:10:20 +0200	[thread overview]
Message-ID: <87blx7phf7.fsf@mouse.gnus.org> (raw)
In-Reply-To: <87sgqjhey5.fsf@gmail.com> (Gustavo Barros's message of "Fri, 02 Aug 2019 10:30:58 -0300")

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 it sounds like it's been a long time since I've used bibtex and has
forgotten most everything about it, that's correct. :-) I've now Cc'd
the bibtex maintainer.)

> If we customize `bibtex-entry-format` by just removing
> `numerical-fields` from it with:
>
>    (setq bibtex-entry-format
> 	  '(opts-or-alts required-fields))
>
> We then get from `bibtex-clean-entry`:
>
>    @Article{Author2019c,
>      author       = {Author},
>      title        = {Title},
>      journaltitle = {Journal title},
>      date         = {2019},
>    }
>
> Besides, to the best of my knowledge, the default of striping braces
> of numerical fields is also not problematic for biblatex or biber.
> And I see no reason why latexmk would have any special implications on
> the case.

> I expressed myself poorly here.  Of course the docstring is built-in
> documentation.  What I meant to say is that there appears to be no
> info document for bibtex-mode.

Yes, the manual just refers to the doc string:

---
Bib@TeX{} mode is a major mode for Bib@TeX{} files, which are commonly
used for keeping bibliographic references for @LaTeX{} documents.  For
more information, see the documentation string for the command
@code{bibtex-mode}.
---

> But I might well be drifting from the OP here.  From a strict
> perspective, the message is: I cannot (currently) reproduce the
> problem, it is likely just a customization issue, and even the default
> behavior of bibtex-mode should not make biblatex/biber choke.

Right.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-08-02 18:10 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 [this message]
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

  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=87blx7phf7.fsf@mouse.gnus.org \
    --to=larsi@gnus.org \
    --cc=21099@debbugs.gnu.org \
    --cc=brian.zbr@gmail.com \
    --cc=gusbrs.2016@gmail.com \
    --cc=winkler@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.
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).