From: Nicolas Goaziou <email@example.com>
To: "Bruce D'Arcus" <firstname.lastname@example.org>
Cc: org-mode-email <email@example.com>
Subject: Re: [org-mode] make citation object available to org-cite-make-insert-processor SELECT-STYLE?
Date: Wed, 11 Aug 2021 12:13:36 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <CAF-FPGOnNzgeWG17sdwtVDtY6qWdd2Q05mhUCsXy+EW_=-716A@mail.gmail.com> (Bruce D'Arcus's message of "Thu, 29 Jul 2021 20:57:52 -0400")
"Bruce D'Arcus" <email@example.com> writes:
> So the idea is to present a preview of the style/variant output when
> selecting the style.
> / (Doe, 2019)
> ... or maybe even multiple columns:
> / (Doe, 2019) \citep
> I'm thinking the best way to build this UI is to iterate through
> org-cite-support-styles, and run at least the default export processes
> to create that preview annotation,
> As my thinking has evolved (and there's been a lot of discussion on
> this the past week), I see two options:
> 1. Generate the previews from the citations at point. This was the
> idea that promoted the suggestion here, since I can't get access to
> that citation data if I use org-cite-make-insert-processor.
> 2. Instead, have a standardized example record just for the preview.
> With this approach, the citation context isn't relevant.
> As to your question, do any style UIs currently allow you to select a
> style on a new citation before selecting the keys?
I added a citation argument to select-style. Let me know if it works for you.
prev parent reply other threads:[~2021-08-11 10:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 13:25 [org-mode] make citation object available to org-cite-make-insert-processor SELECT-STYLE? Bruce D'Arcus
2021-07-29 19:28 ` Nicolas Goaziou
2021-07-30 0:57 ` Bruce D'Arcus
2021-07-30 1:19 ` John Kitchin
2021-08-11 10:13 ` Nicolas Goaziou [this message]
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).