unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Roland Winkler <winkler@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Cletip Cletip <clement020302@gmail.com>, 57246@debbugs.gnu.org
Subject: bug#57246: biblatex don't recognize video type entry
Date: Wed, 17 Aug 2022 17:55:49 -0500	[thread overview]
Message-ID: <87tu6acwei.fsf@gnu.org> (raw)
In-Reply-To: <87v8qrglny.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 17 Aug 2022 13:21:53 +0200")

On Wed, Aug 17 2022, Lars Ingebrigtsen wrote:
> Cletip Cletip <clement020302@gmail.com> writes:
>
>> It's all in the object: biblatex does not recognize inputs of type "video".
>> I think that the bibtex-biblatex-entry-alist variable (and maybe
>> bibtex-biblatex-field-alist) should be modified
>
> Perhaps Roland has some comments here; added to the CCs.

I believe these are non-standard biblatex entries with incomplete
biblatex support.

In Emacs BibTeX mode the problem is here that all biblatex entry types
are defined via the rather "big" user variable
bibtex-biblatex-entry-alist.  So the idea is that users can customize
this variable and define additional entry types.  However, this is not a
very practical strategy.  From a technical perspective, there is still
bug#53606.  Also, as biblatex evolves, the default value of
bibtex-biblatex-entry-alist is continuously updated with each release of
Emacs.  (Usually this refers to small changes concerning biblatex entry
types that are already defined via this variable.)  However, if a user
customizes this variable in whatever way, she will miss the updated
default value when the next release of emacs is shipped.

I believe, these problems are not specific to BibTeX mode.  There are
several "big" user variables in Auctex where I am splicing my custom
elements into an alist instead of using the customize machinery.  This
is not a very user-friendly approach.

Often such "big" user variables are alists.  Sometimes I have been
wondering whether the customize machinery could provide special support
for alists that allows one to modify or add individual cons cells
without touching other cells that are part of the default value.  Then
if a new release of emacs uses updated values for such user variables,
there are less opportunities for how this may collide with individual
customizations.

Would that be useful?

In the present context, a simpler strategy would be to define a new user
variable bibtex-biblatex-extra-entry-alist that complements / overrides
the defaults in bibtex-biblatex-entry-alist.





  reply	other threads:[~2022-08-17 22:55 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 [this message]
2022-08-18  0:52     ` Stefan Kangas
2022-08-18  3:12       ` Roland Winkler
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=87tu6acwei.fsf@gnu.org \
    --to=winkler@gnu.org \
    --cc=57246@debbugs.gnu.org \
    --cc=clement020302@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 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).