From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: Tom Gillespie <tgbugs@gmail.com>, org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: Expanding how the new cite syntax is used to include cross-references - thoughts?
Date: Thu, 12 Aug 2021 11:23:10 -0400 [thread overview]
Message-ID: <CAF-FPGMukXpeSt4k4pbR3=wbuMJjuradJQ=VLtUF+p==xmZD=Q@mail.gmail.com> (raw)
In-Reply-To: <m2eeb0oy3q.fsf@andrew.cmu.edu>
On Wed, Aug 11, 2021 at 1:31 PM John Kitchin <jkitchin@andrew.cmu.edu> wrote:
...
> > It's just there needs to be some way to distinguish among types of
> > targets, I think.
>
> At the risk of repeating myself, I don't think this is true.
Just to clarify ...yes, I agree with you; I wrote that before the
subsequent back-and-forth yesterday.
So no need to repeat: we are now in closer agreement than we were
before the discussion :-)
> As I have thought about this more, the line between citations and
> cross-references has blurred. In org-ref, they were handled the same
> way, with org-links (although each link had its own export function).
> For both cites and refs, the links are just pointers, and in both cases
> it is possible for them to point to things within the same document.
> Even in LaTeX, when we submit a manuscript, the citation references are
> embedded in a standalone tex file, so every link is to an internal
> location.
Let's step back though:
What is the ideal UX for org users?
Per my response to Timothy yesterday, and what I have said elsewhere
about how citations and cross-references are handled elsewhere in the
software universe, I think it's not to remove the distinction, but
rather to clarify it.
In effect, the choice is between:
1. org-cite-insert for both citations and cross-refernces
2. org-cite-insert for the former, org-ref-insert for the latter
Even in org-ref, you adopted 2.; there's a separate command and menu
entry for each, and a different UI.
Do you now think that was a bad decision in retrospect?
Bruce
next prev parent reply other threads:[~2021-08-12 15:24 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 [this message]
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
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-FPGMukXpeSt4k4pbR3=wbuMJjuradJQ=VLtUF+p==xmZD=Q@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).