unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Roland Winkler <winkler@gnu.org>
To: Leo Stein <leo.stein@gmail.com>
Cc: Leonard Lausen <leonard@lausen.nl>, 51621@debbugs.gnu.org
Subject: bug#51621: 29.0.50; bibtex.el biblatex "2.1.3 Non-standard Types" support
Date: Tue, 03 Dec 2024 14:37:39 -0600	[thread overview]
Message-ID: <87jzcgjyek.fsf@gnu.org> (raw)
In-Reply-To: <CAE56pjF_zjiCZfKRK-7UdCj2G+YLmkn2xuUgc0eGOHUO=dufsg@mail.gmail.com> (Leo Stein's message of "Mon, 2 Dec 2024 11:23:31 -0600")

On Mon, Dec 02 2024, Leo Stein wrote:
> I really wish this was more permissive. Looking at a .bib file, we
> have no way of knowing the biblio style that it's going to be set
> with. We also have no way of knowing whether the user is going to
> parse it with bibtex or biber.

The user needs to know whether she wants to use a bib file with BibTeX
or biblatex and use entry types these programs can handle.  Bibtex-mode
cannot be blamed for this.

> I am still missing something... as far as I can tell, the "dialect" is
> just controlling which entries are valid. Is that right? But this is
> not within the purview of whether we use bibtex, or biber+biblatex. It
> depends on the biblio style that the user wants to use for setting
> their bibliography.

Beyond the defaults documented for BibTeX and biblatex, you are free to
write your own bst style files, and you are free to customize
bibtex-mode to your liking.  Everything we discuss here refers only to
user options of bibtex-mode.

The defaults of bibtex-mode match the defaults specified in the
documentation of BibTeX and biblatex.  It would be confusing for users
of bibtex-mode to deviate from that.

> I'm happy to hear that there will be future improvements. 

The goal is to facilitate the customization of bibtex-mode.  I see no
reason to change the defaults of user variables.

> I sincerely request that parsing of entries be made more permissive —
> not restricted to a list of entry types, or relying on the user to
> make some customizations [I think most users are not going to discover
> that it's possible to customize this].

It is a basic aspect of Emacs that users can customize its behavior.
But Emacs cannot (yet) read the mind of its users and foresee the
customizations they want.

I have heard rumors that reading the users' mind will become a user
option in Emacs 42.  (But I do not know whether this option will be
enabled by default.)





  reply	other threads:[~2024-12-03 20:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05 23:35 bug#51621: 29.0.50; bibtex.el biblatex "2.1.3 Non-standard Types" support Leonard Lausen
2021-11-07  3:37 ` Roland Winkler
2024-12-01  4:33 ` Leo Stein
2024-12-02 14:05 ` Roland Winkler
2024-12-02 17:23   ` Leo Stein
2024-12-03 20:37     ` Roland Winkler [this message]
2024-12-03 21:12       ` Leo Stein

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=87jzcgjyek.fsf@gnu.org \
    --to=winkler@gnu.org \
    --cc=51621@debbugs.gnu.org \
    --cc=leo.stein@gmail.com \
    --cc=leonard@lausen.nl \
    /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).