From: Timothy <tecosaur@gmail.com>
To: emacs-orgmode@gnu.org, Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: [wip-cite-new] Merging tomorrow?
Date: Fri, 09 Jul 2021 15:58:45 +0800 [thread overview]
Message-ID: <87fswnx6iy.fsf@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2107081729260.29232@shell3.miskatonic.org>
Hi Nicolas,
In light of all the thoughts expressed on referencing, I no longer think it's a
good idea to have referencing capabilities in wip-cite-new.
I think referencing should get a bit of attention, as citation has here, but a
much smaller separate effort now appears more appropriate to me. This could be
as simple as a way of handling links to named images/tables/etc. when
exporting.
Update: I see wip-cite-new has been merged 🎉. Still sending this
because I think my sentiment is worth sharing and I'd like to prompt a
discussion on references (I'll probably give this a bit of a think then
start a new thread in a few days).
--
Timothy
William Denton <wtd@pobox.com> writes:
> On 8 July 2021, Bruce D'Arcus wrote:
>
>> And the implementation challenges raised by John Kitchin and Joost
>> Kremers (namely the candidate list is different) make this better to
>> deal with using a different mechanism.
>>
>> As a package developer that supports org-cite, I really don't want to
>> be worrying about internal references and such.
>>
>> And as a user, I don't see the benefit of doing so.
>>
>> Effectively, these seem more like org internal links.
>
> I agree with all this. Personally, I'd never expect a citation system like this
> to handle internal references. The way librarians think about citations and
> referencing, these are different.
>
>
> Bill
--
Timothy
next prev parent reply other threads:[~2021-07-09 7:59 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
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 [this message]
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=87fswnx6iy.fsf@gmail.com \
--to=tecosaur@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).