emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Timothy <tecosaur@gmail.com>
To: Bruce D'Arcus <bdarcus@gmail.com>
Cc: emacs-orgmode@gnu.org, Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: [org-cite] autoload oc processors?
Date: Tue, 30 Nov 2021 03:04:34 +0800	[thread overview]
Message-ID: <878rx6pymb.fsf@gmail.com> (raw)
In-Reply-To: <CAF-FPGONtQbQgaxEHvj2yg5ogmn+_rhDhfDuph1PnRV2WZ=7Lg@mail.gmail.com>

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

Hi Bruce,

> Primarily I am asking if there’s a way to load the processor as needed
> without a user explicitly having to do so.

This is actually a thought that occurred to me recently, and I’ve been
considering bringing up on the ML. Thanks for mentioning this.

A more sophisticated solution probably exists, but my thought was that if a cite
export keyword like this is seen:
┌────
│ #+cite_export: FORMAT ...
└────

and there is no known cite backend `FORMAT', then we could just try running
┌────
│ (require 'oc-FORMAT nil t)
└────

before complaining that there’s no cite backend FORMAT loaded.

This relies on consistent naming, but since that seems to hold pretty well so
far and failure to load just results in the current behaviour, I’m inclined to
think this would be a good change in terms of user experience.

All the best,
Timothy

  reply	other threads:[~2021-11-29 19:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-28 21:59 [org-cite] autoload oc processors? Bruce D'Arcus
2021-11-28 22:19 ` Nicolas Goaziou
2021-11-29 13:36   ` Bruce D'Arcus
2021-11-29 19:04     ` Timothy [this message]
2021-11-29 22:48       ` Nicolas Goaziou
2021-11-30  9:56         ` Denis Maier
2021-11-29 22:08     ` Nicolas Goaziou

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=878rx6pymb.fsf@gmail.com \
    --to=tecosaur@gmail.com \
    --cc=bdarcus@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).