emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Bruce D'Arcus <bdarcus@gmail.com>
Cc: Vikas Rawal <vikasrawal@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [oc] provide style/citation preview?
Date: Fri, 25 Mar 2022 08:43:47 -0400	[thread overview]
Message-ID: <m27d8iur8a.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <CAF-FPGO_aYGviyr46UMac5yQWv3QZcvVWn6nhCED20KkEBK=-w@mail.gmail.com>

I think this kind of preview is well-suited for external packages.

There is a subtle point I ran into with this preview approach though,
and that is what is the backend export you want to see? People expect
one source (org) to export to different backends, and even use one
source to make a PDF and HTML (and maybe others). Now it also possible
to use different citation styles for different backends, and the
backends may use different citation processors (e.g. bib(la)tex or CSL).
I felt this was too complex to try to get right in one package. External
packages could provide any subset of these they want, e.g. the way
https://github.com/andras-simonyi/org-cite-csl-activate does. My opinion
of course.

I think the basic CSL styled citation tooltip that is independent of the
final state is a good compromise. The point is to give enough context
about the key to tell you what it is without visiting the source, and if
you need more, you go visit the source (bibtex file, org file, etc.).

"Bruce D'Arcus" <bdarcus@gmail.com> writes:

> On Thu, Mar 24, 2022 at 12:33 PM Vikas Rawal <vikasrawal@gmail.com> wrote:
>>> 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?
>> Some kind of overlay that shows citations as they would (at least as close as possible) look in the export?
> Something like this?
> https://github.com/andras-simonyi/org-cite-csl-activate
> I think he was hoping to incorporate that into the oc-csl processor at
> some point, and that would indeed be another approach to in-buffer
> previewing.
> The issue I have is more just generating the preview content for
> incorporation into the completion annotations.
> Bruce

Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
Pronouns: he/him/his

  parent reply	other threads:[~2022-03-25 12:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24 13:46 [oc] provide style/citation preview? Bruce D'Arcus
     [not found] ` <CALtzAB3Wh9dp_5ik3wN5JA2WmYb-cOoJ7AEKKkUfTXRuKC_5qQ@mail.gmail.com>
2022-03-24 16:32   ` Fwd: " Vikas Rawal
2022-03-24 16:49     ` Bruce D'Arcus
2022-03-24 23:25       ` Vikas Rawal
2022-03-25 12:43       ` John Kitchin [this message]
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=m27d8iur8a.fsf@andrew.cmu.edu \
    --to=jkitchin@andrew.cmu.edu \
    --cc=bdarcus@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=vikasrawal@gmail.com \


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