From: Colin Baxter <firstname.lastname@example.org>
To: "Bruce D'Arcus" <email@example.com>
Cc: , autofrettage <firstname.lastname@example.org>,
Subject: Re: "Unknown processor biblatex"
Date: Mon, 04 Oct 2021 08:18:32 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <CAF-FPGP0EY7t9QMdTXsis_e7SFDcAXB3Ewk0MTP6Xv=kJjMpmA@mail.gmail.com> (Bruce D'Arcus's message of "Sun, 3 Oct 2021 17:09:34 -0400")
>>>>> Bruce D'Arcus <firstname.lastname@example.org> writes:
> On Sun, Oct 3, 2021 at 4:57 PM autofrettage <email@example.com> wrote:
>> Hi all,
>> I have really seen forward to the release of org mode 9.5 with
>> its new and shiny support for citations. The initial frenzy of
>> experimentation has lead to mixed results.
>> Right now I am trying to use the biblatex processor, but I only
>> get "Unknown processor biblatex". How is that even possible, when
>> that should be one of the processors provided by org mode 9.5?
>> Are there more packages, like citeproc.el, on which org-cite
>> depends, and I have to install manually? Is there some mandatory
>> set-up I have failed to notice?
>> I have tried to read
>> https://blog.tecosaur.com/tmio/2021-07-31-citations.html and the
>> manual page for the citations, but I am at my wits' end now.
>> Any pointer would be appreciated.
> You have to load oc-biblatex, say using use-package, and also set
> org-cite-export-processors, like:
> (setq org-cite-export-processors '((latex biblatex) (t csl)))
Great, but what about old timers like me who insist on using bibtex?
I sympathise with the op in not getting this new org-cite to
work. It has beaten me despite repeated efforts.
next prev parent reply other threads:[~2021-10-04 7:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 20:56 "Unknown processor biblatex" autofrettage
2021-10-03 21:09 ` Bruce D'Arcus
2021-10-03 21:22 ` autofrettage
2021-10-04 7:18 ` Colin Baxter [this message]
2021-10-04 8:59 ` Nicolas Goaziou
2021-10-04 9:35 ` Colin Baxter
2021-10-04 11:11 ` Eric S Fraga
2021-10-04 13:36 ` Colin Baxter
2021-10-04 14:00 ` Eric S Fraga
2021-10-04 14:34 ` Max Nikulin
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).