From: Timothy <tecosaur@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: org-mode-email <emacs-orgmode@gnu.org>,
Bruce D'Arcus <bdarcus@gmail.com>
Subject: Re: [wip-cite-new] Merging tomorrow?
Date: Thu, 08 Jul 2021 21:31:50 +0800 [thread overview]
Message-ID: <877di0zzs9.fsf@gmail.com> (raw)
In-Reply-To: <87zguxnlsl.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1762 bytes --]
Hi Nicolas,
> 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.
This very much depends on how you view references vs citations. I personally
think of references as in-text citations (i.e. you’re citing other bits of the
very same document), but I doubt this is a common view (as suggested by other
replies).
To try to lay out what one may expect with references, I’d think some support in
Org (without org-ref et. al) would be good (at least for exporting) — but I’m
not sure what a good for would be.
I think it could be treated similarly to citations, given a variant syntax like
[<ref:#name>] or even just be added as a way of exporting links to named
figures/tables (i.e. ).
It’s a bit late to bring this up, but in case this should come under the
citation umbrella I thought I should.
Lastly, an example of what I’d expect when exporting to ascii (with three
example syntaxes):
┌────
│ #+name: sometab
│ #+caption: Some table
│ | a | b |
│ | c | d |
│
│ Hey, look at [[sometab]]. (or)
│ Hey, look at [cite:#sometab]. (or)
│ Hey, look at [ref:sometab].
└────
┌────
│ ━━━━━━
│ a b
│ c d
│ ━━━━━━
│ Table 1: Some table
│
│ Hey, look at Table 1.
└────
I hope this clears up what I was thinking.
All the best,
*Timothy*
next prev parent reply other threads:[~2021-07-08 13:44 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 [this message]
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=877di0zzs9.fsf@gmail.com \
--to=tecosaur@gmail.com \
--cc=bdarcus@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).