From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: Timothy <tecosaur@gmail.com>
Cc: Tom Gillespie <tgbugs@gmail.com>,
org-mode-email <emacs-orgmode@gnu.org>,
John Kitchin <jkitchin@andrew.cmu.edu>
Subject: Re: Expanding how the new cite syntax is used to include cross-references - thoughts?
Date: Wed, 11 Aug 2021 12:26:11 -0400 [thread overview]
Message-ID: <CAF-FPGMDxGh9Q08t_M_gQ=bhew2jBfEHvz95F8qHdTd1ATQajw@mail.gmail.com> (raw)
In-Reply-To: <87h7fwc697.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 399 bytes --]
That'd be my preferred solution, with (notwithstanding name overlap with
org-ref) an org-ref-insert entry point.
On Wed, Aug 11, 2021, 12:10 PM Timothy <tecosaur@gmail.com> wrote:
> Hi Bruce, John,
>
> Regarding the issues with overloading [cite:@] syntax, would it be too
> much to
> introduce [ref:@] which would function identically, but deal with
> references?
>
> All the best,
> *Timothy*
>
[-- Attachment #2: Type: text/html, Size: 680 bytes --]
next prev parent reply other threads:[~2021-08-11 16:27 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 [this message]
2021-08-11 14:13 ` John Kitchin
2021-08-12 15:23 ` Bruce D'Arcus
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-FPGMDxGh9Q08t_M_gQ=bhew2jBfEHvz95F8qHdTd1ATQajw@mail.gmail.com' \
--to=bdarcus@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
--cc=tecosaur@gmail.com \
--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).