From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [wip-cite-new] Quick note about citation insertion
Date: Fri, 2 Jul 2021 15:47:20 -0400 [thread overview]
Message-ID: <CAF-FPGNptfuFzH51dfM8ZxnVAQkfYs45TKCGrFnPm0XJ8Asrgg@mail.gmail.com> (raw)
In-Reply-To: <87r1ggu25x.fsf@nicolasgoaziou.fr>
Also:
1. I don't see a way to add a key to an existing citation. Editing an
existing key uses completing-read, rather than
completing-read-multiple (as for a new citation), and places point
after the existing key means the style editing UI will pop up.
2. If I use CRM to add multiple keys, for reasons I haven't
determined, I get a "match required" error if I complete the second
key. I can only get it to work if I hit enter before fully completing
the key. I don't know if this is just some selectrum oddity/bug or
not.
On Fri, Jul 2, 2021 at 12:11 PM Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>
> Hello,
>
> I just added an interface to unify functions responsible for inserting
> citations in a buffer. The default binding is <C-c C-x @>.
>
> I also plugged a rather crude function with that interface. In order to
> use it, you can evaluate:
>
> (setq org-cite-insert-processor 'basic)
>
> Internally, this will bind <C-c C-x @> to `org-cite-basic-insert', which
> can insert citations, or edit existing ones, depending on the point.
>
> From a developer point of view, you can specify two new keywords when
> registering a new processor: :insert and :cite-styles. See
> `org-cite-register-processor' for details. See also an application in
> "oc-basic.el", for example.
>
> Regards,
> --
> Nicolas Goaziou
>
next prev parent reply other threads:[~2021-07-02 19:48 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 16:10 [wip-cite-new] Quick note about citation insertion Nicolas Goaziou
2021-07-02 19:21 ` Bruce D'Arcus
2021-07-02 20:05 ` Nicolas Goaziou
2021-07-03 8:45 ` Bruce D'Arcus
2021-07-03 9:20 ` Nicolas Goaziou
2021-07-03 9:56 ` Bruce D'Arcus
2021-07-02 19:47 ` Bruce D'Arcus [this message]
2021-07-02 20:14 ` Nicolas Goaziou
2021-07-02 20:58 ` Bruce D'Arcus
2021-07-02 21:05 ` John Kitchin
2021-07-02 21:21 ` Nicolas Goaziou
2021-07-03 0:21 ` Bruce D'Arcus
2021-07-02 21:48 ` Nicolas Goaziou
2021-07-02 21:57 ` Bruce D'Arcus
2021-07-02 22:33 ` Nicolas Goaziou
2021-07-02 23:59 ` Bruce D'Arcus
2021-07-03 7:28 ` Eric S Fraga
2021-07-03 7:58 ` Nicolas Goaziou
2021-07-03 14:57 ` Eric S Fraga
2021-07-03 15:09 ` Bruce D'Arcus
2021-07-05 13:29 ` Eric S Fraga
2021-07-06 12:11 ` Bruce D'Arcus
2021-07-07 22:59 ` Nicolas Goaziou
2021-07-08 0:38 ` Bruce D'Arcus
2021-07-08 11:46 ` Nicolas Goaziou
2021-07-08 11:52 ` Bruce D'Arcus
2021-07-08 13:19 ` Bruce D'Arcus
2021-07-08 11:41 ` Bruce D'Arcus
2021-07-08 11:44 ` Nicolas Goaziou
2021-09-26 10:40 ` Bastien
2021-07-08 12:48 ` Eric S Fraga
2021-07-08 13:04 ` Bruce D'Arcus
2021-07-08 15:34 ` Eric S Fraga
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-FPGNptfuFzH51dfM8ZxnVAQkfYs45TKCGrFnPm0XJ8Asrgg@mail.gmail.com \
--to=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).