From: "Bruce D'Arcus" <email@example.com>
To: org-mode-email <firstname.lastname@example.org>
Subject: [org-cite] request for coding help on a capf to insert citation key
Date: Sat, 5 Jun 2021 12:13:04 -0400 [thread overview]
Message-ID: <CAF-FPGNKumD+c0onD3bzp=DCt26B4RffXtZC6JsH2PVi2nb9tQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]
I've been struggling with this for a while, and am a mediocre programmer,
so thought I'd ask for help here.
I started out writing this generate capf to insert citation keys, but have
decided to make it specific to org-cite.
Here's the commented function.
Note the "candidates" variable accesses a cached alist, of the form:
("long search string with title, author, etc." . "citekey")
So I want the user to be able to select on the car, but insert the cdr.
(defun bibtex-actions-complete-key-at-point-oc ()
"Complete org-cite citation key at point.
When inserting '@' in a buffer the capf UI will present user with
a list of entries, from which they can narrow against a string
which includes title, author, etc., and then select one. This
function will then return the key 'key', resulting in '@key' at
;; FIX exit-function is wrong; results in "no match"
;; TODO tighten this regex for org-cite
(when (looking-back "@[a-zA-Z]+" 5)
(let* ((candidates (bibtex-actions--get-candidates))
(begin (save-excursion (backward-word) (point)))
(list begin end candidates :exclusive 'no
(lambda (chosen status)
(when (eq status 'finished)
(cdr (assoc chosen candidates))))))))
[-- Attachment #2: Type: text/html, Size: 1827 bytes --]
next reply other threads:[~2021-06-05 16:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-05 16:13 Bruce D'Arcus [this message]
2021-06-05 21:14 ` [org-cite] request for coding help on a capf to insert citation key Bruce D'Arcus
2021-06-06 16:21 ` Bruce D'Arcus
2021-06-21 14:16 ` Bruce D'Arcus
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).