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" <bdar...@gmail.com> writes: > On Thu, Mar 24, 2022 at 12:33 PM Vikas Rawal <vikasra...@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 412-268-7803 @johnkitchin http://kitchingroup.cheme.cmu.edu Pronouns: he/him/his