emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: org-mode-email <emacs-orgmode@gnu.org>
Subject: [oc] provide style/citation preview?
Date: Thu, 24 Mar 2022 09:46:18 -0400	[thread overview]
Message-ID: <CAF-FPGOrWUwc6iB3pr9JD04W=H1kAU0LY+BQ89jddewx1zieqg@mail.gmail.com> (raw)

This is an idea related to an issue John Kitchin and I were trying to
sort out a few months back, that he mentioned in another thread.


The question is how to help users understand the relation between oc
styles and target output.

There are two places where this matters:

1. selecting the style (say in a completion list)
2. previewing the citation after the fact (for example, hovering over
it in the buffer)

On 2, right now in oc-basic, if one hovers over a key, one gets a
tooltip preview of the rendered bibliographic entry, which is very

Picking up an idea that John mentioned in the above message, would it
be feasible when hovering over the prefix (the part before the colon)
to get a preview of the citation? By "feasible" I mean a good idea
from a UX POV, and without any obvious performance penalties.

As for the point he raises about which export backend to preview,
perhaps that should just be via a "citation-preview" defcustom?

So if one selected, say, natbib, one would see something like "\textt"
in the tooltip.

On 1, in citar I currently have a UI with a grouped list of
style/variants, and a user-defined static preview for each, something
like this:

--------- default ------------
/                         (de Ville, 2020)
----------- text --------------
/text                   de Ville (2020)
/text/caps           De Ville (2020)

So I'm just wondering how best to dynamically generate those previews,
perhaps even just using a pre-selected reference*, and if maybe oc
could make that easier?

* One wrinkle in general here is that in the LaTeX intermediate export
targets, you really don't care about the reference data, or even the
key; you just care about what the command is. With the CSL rendered
output, you do care about that.


             reply	other threads:[~2022-03-24 13:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24 13:46 Bruce D'Arcus [this message]
     [not found] ` <CALtzAB3Wh9dp_5ik3wN5JA2WmYb-cOoJ7AEKKkUfTXRuKC_5qQ@mail.gmail.com>
2022-03-24 16:32   ` Fwd: [oc] provide style/citation preview? Vikas Rawal
2022-03-24 16:49     ` Bruce D'Arcus
2022-03-24 23:25       ` Vikas Rawal
2022-03-25 12:43       ` John Kitchin
2022-03-25 17:48         ` Bruce D'Arcus

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:

  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-FPGOrWUwc6iB3pr9JD04W=H1kAU0LY+BQ89jddewx1zieqg@mail.gmail.com' \
    --to=bdarcus@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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).