From: Roland Winkler <winkler@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
Cletip Cletip <clement020302@gmail.com>,
57246@debbugs.gnu.org
Subject: bug#57246: biblatex don't recognize video type entry
Date: Wed, 17 Aug 2022 22:12:17 -0500 [thread overview]
Message-ID: <87tu6ab5ym.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmnAykqs7vJxxxD6bAAxo9Gc_gEWAJg8PUME7v_e0exm+g@mail.gmail.com> (Stefan Kangas's message of "Wed, 17 Aug 2022 17:52:57 -0700")
On Wed, Aug 17 2022, Stefan Kangas wrote:
> How about just having two variables instead? One for users, and one for
> the mode itself.
That's certainly an option (see the last paragraph of my message).
Is there a possibility to declare the customizability of a variable
obsolete? bibtex-biblatex-entry-alist has been around as a user
variable for more than ten years and bibtex-BibTeX-entry-alist for yet
many more years. I doubt that many people ever tried to customize these
variables. Still, if we add new dedicated user variables, it would be
nice to tell users that the customization of the old variables has been
depreciated.
next prev parent reply other threads:[~2022-08-18 3:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 17:08 bug#57246: biblatex don't recognize video type entry Cletip Cletip
2022-08-17 11:21 ` Lars Ingebrigtsen
2022-08-17 22:55 ` Roland Winkler
2022-08-18 0:52 ` Stefan Kangas
2022-08-18 3:12 ` Roland Winkler [this message]
2022-08-18 8:53 ` Arash Esbati
2022-08-18 17:06 ` Roland Winkler
2022-08-18 9:08 ` Stefan Kangas
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=87tu6ab5ym.fsf@gnu.org \
--to=winkler@gnu.org \
--cc=57246@debbugs.gnu.org \
--cc=clement020302@gmail.com \
--cc=larsi@gnus.org \
--cc=stefankangas@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 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).