From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: org-mode-email <emacs-orgmode@gnu.org>, Timothy <tecosaur@gmail.com>
Subject: Re: [wip-cite-new] Merging tomorrow?
Date: Thu, 8 Jul 2021 07:15:23 -0400 [thread overview]
Message-ID: <CAF-FPGPG=gb5JCjcUL89uvKt-bNA4FpF3fx6FhBgTR78S1dFvg@mail.gmail.com> (raw)
In-Reply-To: <87zguxnlsl.fsf@nicolasgoaziou.fr>
On Thu, Jul 8, 2021 at 6:26 AM Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>
> Hello,
>
> Timothy <tecosaur@gmail.com> writes:
>
> > Bruce D'Arcus <bdarcus@gmail.com> writes:
> >
> >>> wip-cite-new deals with citing from bibliographies, but I don't think it
> >>> deals with within-document referencing --- should it?
> >
> >> 1. Should it?
> >> 1. Maybe.
> >
> > I feel like it would fit. With everything that's been done for
> > citations, this feels like it may be a rather minor addition (or at
> > least this is what I hope).
> >
> >> 2. Can it? Could the design be extended to include internal referencing?
> >> 2. I think so. You'd just need a way to include internal targets in
> >> addition to the citation-references (keys); for illustration,
> >> something like [cite:#some-if].
> >
> > I can't claim to have thought about this that much either, but something
> > like [cite:#some-fig] would seem to fit.
> >
> >> 3. If yes to both, should that hold back merger now?
> >> 3. No.
> >
> > I don't think this should hold up the merge either, but it's relevant in
> > the overall nature of the feature and perhaps could be shoehorned in
> > following the merge? I feel like this is one small quite simple case and
> > most of the thinking required has already been done. I'm not sure
> > though, I'd go with whatever Nic's thought are on this.
>
> At this point, I don't have enough understanding of the problem to have
> an opinion. IIUC, your example does not even mention citations. How
> should it be used, what should be the output in LaTeX, and in UTF-8
> export? This is not clear to me.
>
> What can I say however is: if this feature implies to change, or extend,
> syntax, then it is /de facto/ a blocker for the merge, and needs to be
> sorted out.
As I was hinting, I don't know this area well either.
I think the first question is the "should" one; whether this is
in-scope of this module.
I wasn't sure, so said "maybe".
Joost says "no."
In latex, such internal references are not citations though; they use
a different mechanism.
Does that not suggest, Timothy, that this might be out-of-scope for
this module; that Joost is right?
Bruce
next prev parent reply other threads:[~2021-07-08 11:16 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 [this message]
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='CAF-FPGPG=gb5JCjcUL89uvKt-bNA4FpF3fx6FhBgTR78S1dFvg@mail.gmail.com' \
--to=bdarcus@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=tecosaur@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).