From: "Bruce D'Arcus" <email@example.com>
To: Nicolas Goaziou <firstname.lastname@example.org>
Cc: org-mode-email <email@example.com>
Subject: Re: [org-cite] add convention for direct commands, process for adding mappings to export processor(s)?
Date: Sun, 10 Oct 2021 16:56:12 -0400 [thread overview]
Message-ID: <CAF-FPGO9FJyiejPVcmbt_1hBC0yR4jb81wdwjuRY3CZQzn9Uiw@mail.gmail.com> (raw)
On Sun, Oct 10, 2021 at 4:41 PM Nicolas Goaziou <firstname.lastname@example.org> wrote:
> >> And if we were to add this, we'd still need to answer my first
> >> question: when and how to add specific style/variant mappings to the
> >> oc processors.
> It is possible to send a patch if it is something useful. Some
> processors (probably only biblatex at this point, we probably cover
> everything in natbib) may also introduce a customizable variable for
> user-defined styles.
Ah yes; that's a better solution.
And I agree; it mostly makes sense for biblatex (though I saw someone
on reddit asking about natbib \bibentry, which is what reminded me
It's not needed for oc-csl, because of the tight integration of that
prev parent reply other threads:[~2021-10-10 20:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 18:37 Bruce D'Arcus
2021-10-10 14:28 ` Bruce D'Arcus
2021-10-10 20:41 ` Nicolas Goaziou
2021-10-10 20:56 ` Bruce D'Arcus [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).