From: Joost Kremers <joostkremers@fastmail.fm>
To: emacs-orgmode@gnu.org
Subject: Re: [wip-cite-new] Merging tomorrow?
Date: Thu, 08 Jul 2021 08:47:15 +0200 [thread overview]
Message-ID: <87v95ll1nv.fsf@fastmail.fm> (raw)
In-Reply-To: <CAF-FPGOBePRC86aF3dSnzRPMBx2K9rHjC0LQTU3QDoguUQQyoA@mail.gmail.com>
On Thu, Jul 08 2021, Bruce D'Arcus wrote:
> On Wed, Jul 7, 2021 at 11:48 PM Timothy <tecosaur@gmail.com> wrote:
>
>> wip-cite-new deals with citing from bibliographies, but I don't think it
>> deals with within-document referencing --- should it?
>
> It doesn't now.
>
> I guess to break down the second question further:
>
> 1. Should it?
One thing to keep in mind here: these are two different sets of functionality
and a tool designed to handle one isn't necessarily right for handling the
other.
Org-cite provides four capabilities: insert, follow, activate and export. And
while they may be very similar conceptually for a user, a provider would need to
handle each of these very differently for citations and in-document references.
And that's the point: while it makes sense for Ebib to provide insert and follow
capabilities for citations, there is really no point in Ebib providing those for
in-document references as well. It doesn't have the infrastructure for it, nor
is Ebib the first (or even second or third) option that comes to mind when you
think about inserting and following in-document references.
I do think it makes sense if such a hypothetical org-new-ref has a very similar
conceptual design to org-cite and a very similar user interface (e.g., the same
keybindings), and perhaps a part of the code can be shared, it should be
possible to register different provides for them.
--
Joost Kremers
Life has its moments
next prev parent reply other threads:[~2021-07-08 7:13 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 0:17 [wip-cite-new] Merging tomorrow? Nicolas Goaziou
2021-07-08 0:29 ` William Denton
2021-07-08 2:12 ` Thomas S. Dye
2021-07-08 3:18 ` Matt Price
2021-07-08 8:12 ` Greg Minshall
2021-07-08 10:09 ` Timothy
2021-07-08 3:47 ` Timothy
2021-07-08 6:31 ` Bruce D'Arcus
2021-07-08 6:47 ` Joost Kremers [this message]
2021-07-08 10:17 ` Timothy
2021-07-08 10:26 ` Nicolas Goaziou
2021-07-08 11:15 ` Bruce D'Arcus
2021-07-08 11:33 ` John Kitchin
2021-07-08 13:31 ` Timothy
2021-07-08 14:27 ` Bruce D'Arcus
2021-07-08 21:31 ` William Denton
2021-07-09 7:58 ` Timothy
2021-07-09 8:06 ` Eric S Fraga
2021-07-08 14:36 ` Nicolas Goaziou
2021-07-08 11:39 ` Eric S Fraga
2021-07-08 7:56 ` Jens Neuhalfen
2021-07-08 11:42 ` Eric S Fraga
2021-07-08 11:50 ` Nicolas Goaziou
2021-07-08 12:49 ` Eric S Fraga
2021-07-09 13:36 ` William Denton
2021-07-09 16:07 ` Eric S Fraga
2021-07-13 15:50 ` John Kitchin
2021-08-20 13:37 ` Eric S Fraga
2021-08-20 13:46 ` Eric S Fraga
2021-08-20 13:47 ` Bruce D'Arcus
2021-08-20 13:55 ` Eric S Fraga
[not found] ` <87eeaonp4x.fsf@ucl.ac.uk>
2021-08-20 15:06 ` Bruce D'Arcus
2021-08-20 15:20 ` John Kitchin
2021-08-20 15:31 ` Bruce D'Arcus
2021-08-20 15:56 ` Eric S Fraga
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=87v95ll1nv.fsf@fastmail.fm \
--to=joostkremers@fastmail.fm \
--cc=emacs-orgmode@gnu.org \
/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).