emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: Tom Gillespie <tgbugs@gmail.com>, Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Expanding how the new cite syntax is used to include cross-references - thoughts?
Date: Tue, 12 Oct 2021 20:08:31 -0400	[thread overview]
Message-ID: <CAF-FPGOZuJJc3KyzLicX2gEPN7yqi2CY1mLRexcKdbw5Tfa8fg@mail.gmail.com> (raw)
In-Reply-To: <CAJ51EToprHaGvnx4_k_RELopwbTBp9sc2-ZvSiC=paJmDqfzHA@mail.gmail.com>

On Tue, Oct 12, 2021 at 7:28 PM John Kitchin <jkitchin@andrew.cmu.edu> wrote:
>
> I am not sure it really fits the model of the exporters that are in org, since it is basically just a pre-processing hook.

[snip]

> It also is (IMO) a part of org-ref since it uses the links that are defined in org-ref. I see it as more an extension of org-mode than something that needs to be in the core. For simple cross-references the built in internal links are adequate I think.
>
> Anyway, it should be tested for a while to see if it is the right way to do this. Maybe there are better ideas for it.

Probably does take more testing and thought, but I guess I was
thinking of something like an org-crossref-insert interactive
function, that could make use of functions like
org-ref-refproc-referenceables, to provide better out-of-box support
for at least inserting cross-references.

Perhaps like org-cite-insert, that could be configurable, so one could
plug in a different such functions.

I was toying with an idea like this earlier:

https://gist.github.com/bdarcus/1cebcff17fca762a363f89138214848d

Bruce


  reply	other threads:[~2021-10-13  0:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11  0:58 Expanding how the new cite syntax is used to include cross-references - thoughts? John Kitchin
2021-08-11  1:19 ` Bruce D'Arcus
2021-08-11  5:28   ` Tom Gillespie
2021-08-11 11:13     ` Bruce D'Arcus
2021-08-11 11:54       ` Bruce D'Arcus
2021-08-11 13:43         ` John Kitchin
2021-08-11 14:32           ` Bruce D'Arcus
2021-08-11 14:56             ` John Kitchin
2021-08-11 15:41               ` Bruce D'Arcus
2021-08-11 16:08                 ` Timothy
2021-08-11 16:26                   ` Bruce D'Arcus
2021-08-11 14:13       ` John Kitchin
2021-08-12 15:23         ` Bruce D'Arcus
2021-08-12 17:19           ` John Kitchin
2021-08-12 18:06             ` Bruce D'Arcus
2021-08-13 15:22             ` Eric S Fraga
2021-10-10 13:30               ` Bruce D'Arcus
2021-10-12 21:16                 ` John Kitchin
2021-10-12 21:58                   ` Bruce D'Arcus
2021-10-12 23:27                     ` John Kitchin
2021-10-13  0:08                       ` Bruce D'Arcus [this message]
2021-08-11 13:23   ` John Kitchin

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=CAF-FPGOZuJJc3KyzLicX2gEPN7yqi2CY1mLRexcKdbw5Tfa8fg@mail.gmail.com \
    --to=bdarcus@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jkitchin@andrew.cmu.edu \
    --cc=tgbugs@gmail.com \
    /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).