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, oc-basic] configurable open-at-point, font-locking when json?
Date: Tue, 08 Jun 2021 22:25:54 +0200 [thread overview]
Message-ID: <87mts0hzn1.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAF-FPGPLC50N3exbR=iw-RDfBT3ci8pf5WXnctq0s-m3NFTOrg@mail.gmail.com> (Bruce D'Arcus's message of "Tue, 8 Jun 2021 09:07:58 -0400")
Hello,
"Bruce D'Arcus" <bdarcus@gmail.com> writes:
> On Tue, Jun 8, 2021 at 7:36 AM Bruce D'Arcus <bdarcus@gmail.com> wrote:
>
>> (org-cite-register-processor 'bibtex
>> :follow #'bibtex-completion-open-any)
>
> Actually, looking at the docstrings, I don't think this will work as
> is, as the follow processor "accepts two arguments, the citation or
> citation reference object at point", while the bibtex-completion
> functions take a list of keys.
>
> So I guess for that I'd need a little wrapper to call that function.
Indeed.
> Still, I'm confused why the basic font-locking doesn't work in this case.
I know it is not terribly useful but… it works here. For example, if no
bibliography is defined, all cite keys are red (error face).
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2021-06-08 20:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 16:53 [org-cite, oc-basic] configurable open-at-point, font-locking when json? Bruce D'Arcus
2021-06-07 18:46 ` Bruce D'Arcus
2021-06-07 21:14 ` Nicolas Goaziou
2021-06-07 21:27 ` Bruce D'Arcus
2021-06-07 21:57 ` Bruce D'Arcus
2021-06-08 9:33 ` Nicolas Goaziou
2021-06-08 11:36 ` Bruce D'Arcus
2021-06-08 13:07 ` Bruce D'Arcus
2021-06-08 20:25 ` Nicolas Goaziou [this message]
2021-06-08 21:02 ` Bruce D'Arcus
2021-06-09 11:32 ` Bruce D'Arcus
2021-06-09 15:46 ` Nicolas Goaziou
2021-06-08 2:20 ` Matt Price
2021-06-08 9:29 ` Nicolas Goaziou
2021-06-08 21:03 ` Matt Price
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=87mts0hzn1.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).