unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Roland Winkler" <winkler@gnu.org>
To: Leonard Lausen <leonard@lausen.nl>
Cc: 51621@debbugs.gnu.org
Subject: bug#51621: 29.0.50; bibtex.el biblatex "2.1.3 Non-standard Types" support
Date: Sat, 06 Nov 2021 22:37:00 -0500	[thread overview]
Message-ID: <87v914ab6r.fsf@gnu.org> (raw)
In-Reply-To: <87v91618i8.fsf@lausen.nl> (Leonard Lausen's message of "Fri, 05 Nov 2021 23:35:11 +0000")

On Fri, Nov 05 2021, Leonard Lausen wrote:
> Would it make sense to add support for these types to bibtex.el?

I myself do not use biblatex.  But it seems to me that the sheer number
of entry types supported by biblatex gets overwhelming and inefficient
for users that may use only a subset of all biblatex entry types.  Could
it make sense to break down the list of biblatex entry types into two
customizable subsets such that commands like bibtex-entry and the menu
"Entry-Types" list only the "important" entry types, whereas functions
like bibtex-validate accept the complete set of entry types supported by
biblatex?

Roland





      reply	other threads:[~2021-11-07  3:37 UTC|newest]

Thread overview: 2+ 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 [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

  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=87v914ab6r.fsf@gnu.org \
    --to=winkler@gnu.org \
    --cc=51621@debbugs.gnu.org \
    --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).