From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: "Bruce D'Arcus" <bdarcus@gmail.com>,
org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: [org-cite, oc-csl] citation fontification and previews?
Date: Fri, 28 May 2021 16:40:39 -0400 [thread overview]
Message-ID: <CAF-FPGMPX3etCeq-UUeLDWwiwLf_ZZyt_Er+EaX46=168HiaTw@mail.gmail.com> (raw)
In-Reply-To: <87im328w92.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]
On Fri, May 28, 2021 at 3:59 PM Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
>
> "Bruce D'Arcus" <bdarcus@gmail.com> writes:
>
> > Beyond requiring oc-basic (or any other "activate" processor), do I
> > need to do anything more to "use" it?
>
> You need to associate it to the "active" capability:
>
> (setq org-cite-activate-processor 'basic)
>
> (or with a file-local variable).
>
> > So then it might be ideal to have oc-csl be such an extensible
> > "activate" processor then?
>
> It could be a good basis.
>
> > From what John has said here, it's likely to be quite awhile before we
> > see an org-ref rewritten for org-cite.
>
> Maybe it provides interface we could write a thin wrapper with, and plug
> it into the activate function.
What would "it" be here?
Org-ref, or pieces of it?
In any case, I was thinking previewing of some sort would be valuable
initially, and as Andras noted, citeproc-el is well-positioned to provide
that.
But it would be natural to potentially want to enhance that functionality
later, as your mention of "extensibility" suggests.
I do in general imagine that org-cite will provide a foundation for smaller
packages that can enhance the functionality in flexible ways; not so much
large monolithic packages, even if those are also possible.
[-- Attachment #2: Type: text/html, Size: 1812 bytes --]
prev parent reply other threads:[~2021-05-28 20:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 12:17 [org-cite, oc-csl] citation fontification and previews? Bruce D'Arcus
2021-05-28 12:27 ` Bruce D'Arcus
2021-05-28 17:43 ` Nicolas Goaziou
2021-05-28 17:55 ` Bruce D'Arcus
2021-05-28 19:59 ` Nicolas Goaziou
2021-05-28 20:40 ` Bruce D'Arcus [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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAF-FPGMPX3etCeq-UUeLDWwiwLf_ZZyt_Er+EaX46=168HiaTw@mail.gmail.com' \
--to=bdarcus@gmail.com \
--cc=emacs-orgmode@gnu.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/org-mode.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).