From: Roland Winkler <winkler@gnu.org>
To: Leo Stein <leo.stein@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: [PATCH] BibTeX-mode: add eprint field as potential source for entry's URL
Date: Tue, 03 Dec 2024 14:38:38 -0600 [thread overview]
Message-ID: <87iks0jycx.fsf@gnu.org> (raw)
In-Reply-To: <CAE56pjFh+v2KY=YSadr3rmTO52Q-Gh=CJLcnDftf=LaBbOWa+g@mail.gmail.com> (Leo Stein's message of "Mon, 2 Dec 2024 11:39:17 -0600")
On Mon, Dec 02 2024, Leo Stein wrote:
> > All this goes beyond old-fashioned BibTeX. But the documentation
> > for biblatex (current: version 3.20 from CTAN) says in Sec. 3.14.7
> > "Electronic Publishing Information" how the field "eprint" should be
> > used in combination with a field "eprinttype" to identify an
> > electronically published document.
>
> This is independent of bibtex vs. biber+biblatex.
The documentation for these programs defines the defaults implemented
via user variables of bibtex-mode. You are free to customize these
variables.
> Physicists, mathematicians, and computer scientists use LaTeX and thus
> bibtex more so than other specialties.
It is beyond me to comment.
> Of course I've customized the variable for myself. But it took me
> years before I realized "Hey, wait a minute, why can't I click on the
> arXiv number?", and then dug through the mode docs to discover that
> it's possible to customize this.
We are talking here about Emacs where 10 users may strongly advocate 20
different "most obvious" ways to change the behavior of Emacs.
prev parent reply other threads:[~2024-12-03 20:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-01 19:05 [PATCH] BibTeX-mode: add eprint field as potential source for entry's URL Leo Stein
2024-12-01 19:49 ` Eli Zaretskii
2024-12-02 13:08 ` Roland Winkler
2024-12-02 13:34 ` Eli Zaretskii
2024-12-02 17:39 ` Leo Stein
2024-12-03 20:38 ` 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=87iks0jycx.fsf@gnu.org \
--to=winkler@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=leo.stein@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).