From: Joost Kremers <firstname.lastname@example.org>
Subject: Question about citation processors [wip-cite branch]
Date: Tue, 04 May 2021 12:41:11 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
As the maintainer of Ebib, I have of course been following the threads on
citation support for Org with some interest. I have not been able to follow
every detail, however, in part probably due to my limited experience with CSL
and citeproc. (I use biblatex myself.)
Now I find myself with some specific questions that I cannot find an answer to.
(Possibly because I'm just daft enough to overlook them in the e-mails Nicolas
sent, but in that case feel free to point this out.)
So, on the assumption that there are Org users out there that may want to use
Ebib to manage their citations, what would Ebib need to do in order to be a good
- A user should be able to insert citations into an Org document. IIUC nothing
in org-cite provides any functionality for this, right? Is there a default
list of styles a user would expect to be supported, or does this depend solely
on the bibliography style one uses?
- =:active= just means "font-lock", right?
- Since I don't plan on writing an exporter, I assume that it is possible to
mix and match processors? Say, have one for the =:follow= property, another
for =:activate= and a third one for =:export-*=?
- What kind of data structure do the =:follow= and =:activate= functions take?
Should I just look at =oc-basic.el= or is this written down somewhere?
- Is there a function or buffer-local variable that gives me a list of all the
bibliography files of a buffer? Related to that: if a user has set
=org-cite-global-bibliography= and also provides a =#+bibliography= keyword,
are both sources used, or only the keyword?
Thanks for any and all comments!
Life has its moments
next reply other threads:[~2021-05-04 13:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 10:41 Joost Kremers [this message]
2021-05-04 13:45 ` Bruce D'Arcus
2021-05-04 14:07 ` Joost Kremers
2021-05-04 15:04 ` Bruce D'Arcus
2021-05-04 15:27 ` Joost Kremers
2021-05-04 19:34 ` Denis Maier
2021-05-04 20:04 ` Joost Kremers
2021-05-04 15:10 ` Bruce D'Arcus
2021-05-04 15:22 ` Joost Kremers
2021-05-04 15:39 ` Bruce D'Arcus
2021-05-04 16:22 ` Nicolas Goaziou
2021-05-04 19:17 ` Joost Kremers
2021-05-05 14:09 ` Nicolas Goaziou
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).