emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Price <moptop99@gmail.com>
To: Matt Price <moptop99@gmail.com>,
	"Bruce D'Arcus" <bdarcus@gmail.com>,
	 org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: [org-cite, oc-basic] configurable open-at-point, font-locking when json?
Date: Tue, 8 Jun 2021 17:03:26 -0400	[thread overview]
Message-ID: <CAN_Dec8+nG-8p4hsGCCim6ua4obB30n0MH3xw7opccUoeagJig@mail.gmail.com> (raw)
In-Reply-To: <8735tsk8l4.fsf@nicolasgoaziou.fr>

[-- Attachment #1: Type: text/plain, Size: 2138 bytes --]

On Tue., Jun. 8, 2021, 5:29 a.m. Nicolas Goaziou, <mail@nicolasgoaziou.fr>

> Hello,
> Matt Price <moptop99@gmail.com> writes:
> > IIUC, the current architecture assigns responsibility for both *citation
> > export* and *in-buffer actions* to a processor shosen by the user (right
> > now, oc-cite, oc-natbib, or oc-csl).
> That's incorrect. The current architecture provides three entry points:
> `activate', `follow' and `export'. A processor can handle any, or all of
> these capabilities. For example, `natbib' processor doesn't provide any
> interface for `follow' or `activate'. OTOH `basic' provides the three of
> them.

Ah. Well then....

> Users can select a different processor for any of the capabilities
> listed above, independently on the others. So you don't have to change,
> for example, the processor responsible for fontification if you are
> swapping processor used for export.

Ahhhhh got it.

> > I guess this will become complicated once there are processors supporting
> > more exotic backends (e.g. Zotero via zotxt), but package managers could
> > handle that in readme's or perhaps with a single defcustom like, maybe,
> > ~org-zotxt-do-cite-setup~, or similar.
> I'm not sure to understand this, as I don't know what zotxt does
> exactly.

Well, I'm not sure it's relevant anymore, but zotxt provides a direct API
to the zotero database, and also an emacs library with functions for
querying and processing that API. All I really meant here is that of org
starts to support this kind of nonstandard backend (in which the
bibliography file isn't actually a file anymore), then the :activate and
:follow functions really will have to be different in buffers using that

> > I also think this will reduce code repetition across the 3 processors,
> and
> > generally simplify life for most users (though initial setup may be more
> > frequent.
> >
> > Have I understood correctly, and if so what do you think of this idea?
> Unless I'm mistaken, your idea is already implemented, isn't it?

Yup. Thanks for the very clear explanation and sorry for the noise.


[-- Attachment #2: Type: text/html, Size: 3449 bytes --]

      reply	other threads:[~2021-06-08 21:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 16:53 [org-cite, oc-basic] configurable open-at-point, font-locking when json? Bruce D'Arcus
2021-06-07 18:46 ` Bruce D'Arcus
2021-06-07 21:14 ` Nicolas Goaziou
2021-06-07 21:27   ` Bruce D'Arcus
2021-06-07 21:57     ` Bruce D'Arcus
2021-06-08  9:33     ` Nicolas Goaziou
2021-06-08 11:36       ` Bruce D'Arcus
2021-06-08 13:07         ` Bruce D'Arcus
2021-06-08 20:25           ` Nicolas Goaziou
2021-06-08 21:02             ` Bruce D'Arcus
2021-06-09 11:32             ` Bruce D'Arcus
2021-06-09 15:46               ` Nicolas Goaziou
2021-06-08  2:20   ` Matt Price
2021-06-08  9:29     ` Nicolas Goaziou
2021-06-08 21:03       ` Matt Price [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:

  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=CAN_Dec8+nG-8p4hsGCCim6ua4obB30n0MH3xw7opccUoeagJig@mail.gmail.com \
    --to=moptop99@gmail.com \
    --cc=bdarcus@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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).