From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Bruce D'Arcus" <bdarcus@gmail.com>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: [org-cite] autoload oc processors?
Date: Sun, 28 Nov 2021 23:19:17 +0100 [thread overview]
Message-ID: <87lf17ordm.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAF-FPGPvmSJq8qJvVP2jR8k6X1dVqHEFDgvOqtcp7_MDu53Djw@mail.gmail.com> (Bruce D'Arcus's message of "Sun, 28 Nov 2021 16:59:09 -0500")
Hello,
"Bruce D'Arcus" <bdarcus@gmail.com> writes:
> Is there any reason not to autoload the processors?
I am not sure about what you mean. Could you elaborate?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2021-11-28 22:19 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 [this message]
2021-11-29 13:36 ` Bruce D'Arcus
2021-11-29 19:04 ` Timothy
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=87lf17ordm.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=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).