From: John Kitchin <email@example.com>
To: "Bruce D'Arcus" <firstname.lastname@example.org>
Cc: Daniel Nemenyi <email@example.com>, org-mode-email <firstname.lastname@example.org>
Subject: Re: Org-cite stuck in Helm minibuffer [9.5.1 (9.5.1-g36086a @ /home/dan/.emacs.d/elpa/org-9.5.1/)]
Date: Mon, 6 Dec 2021 13:09:10 -0500 [thread overview]
Message-ID: <CAJ51ETof=FDCfzaXwztkue_hSOqh-sfy4gdiaPphv8zvKtp19g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2389 bytes --]
You could consider something like this:
The insert processors provided by org-cite use depend only on Emacs and use
completing-read to select one or more citation keys for insertion.
Completing-read is intended for selecting a single item, and org-cite
compensates for this by letting you select multiple keys, and exiting
when the selected candidate is an empty string. With a vanilla Emacs
installation, you can press Tab to see a list of possible candidates, and
use Tab for completion. Each time you press return with a completed
candidate in the minibuffer that key is added to a list to be inserted.
Press return with an empty minibuffer to finish and insert the selected
If you use an alternate completion-backend like helm, ivy, selectrum, etc.
you will see different behavior because they have a different concept of
the selected candidate vs the current input to select the current input
(which must be empty).
With helm, you cannot mark candidates, and there are no alternate actions.
You press return on each entry you want to select, and when you are done
selecting them you press C-return or M-return (bound to
helm-cr-empty-string) to insert all the entries at once.
With ivy, you press return on each entry you want to select, and when you
are done selecting them you press C-M-j (exits with current input instead
of the current candidate) to insert them.
With Selectrum, ... (don't know what the keybinding here is)
(not sure if there are other ones that should also be included)
Other insert processors may use these backends natively, so this
information may not apply to them.
Professor John Kitchin (he/him/his)
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
On Mon, Dec 6, 2021 at 9:43 AM Bruce D'Arcus <email@example.com> wrote:
> On Mon, Dec 6, 2021 at 9:33 AM Daniel Nemenyi <firstname.lastname@example.org> wrote:
> > Apologies, I did ('Thanks org-ref I'm done...'), slip of the tongue.
> Oh, I missed that; sorry John.
> > Could have a go though if someone could give me a pointer? But if this
> is left to the user, perhaps we should include a line in the documentation
> telling them?
> The completion UIs have different keybindings for this. What should
> the documentation say?
[-- Attachment #2: Type: text/html, Size: 3260 bytes --]
next prev parent reply other threads:[~2021-12-06 18:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 12:24 Daniel Nemenyi
2021-12-06 13:09 ` Bruce D'Arcus
2021-12-06 13:22 ` Bruce D'Arcus
2021-12-06 14:27 ` Daniel Nemenyi
2021-12-06 14:39 ` Bruce D'Arcus
2021-12-06 18:09 ` John Kitchin [this message]
2021-12-08 13:13 ` Daniel Nemenyi
2021-12-08 22:33 ` Bruce D'Arcus
2021-12-09 16:26 ` Eric S Fraga
2021-12-06 13:22 ` John Kitchin
2021-12-06 14:21 ` Bruce D'Arcus
2021-12-06 14:23 ` Daniel Nemenyi
2021-12-06 17:58 ` Nicolas Goaziou
2021-12-06 18:32 ` Daniel Nemenyi
2021-12-06 18:54 ` John Kitchin
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 \
* 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).