From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: Tom Gillespie <tgbugs@gmail.com>
Cc: 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 07:54:05 -0400 [thread overview]
Message-ID: <CAF-FPGOxYLKk+UkWVfoV75cCv_TZYeWDi25zxR60B9zdLorD2g@mail.gmail.com> (raw)
In-Reply-To: <CAF-FPGNVjfcwyHTOu32JavzG-yWvweCF5fY5xdX+KmYgKESeAA@mail.gmail.com>
On Wed, Aug 11, 2021 at 7:13 AM Bruce D'Arcus <bdarcus@gmail.com> wrote:
> Is there a workaround for this somehow, or an alternative that gets
> the same thing in the end?
Like, if not typing the link, type the target?
From this example from org-mode manual, the "fig" in the name keyword
could provide that type?
#+CAPTION: This is the caption for the next figure link (or table)
#+NAME: fig:SED-HR4049
[[./img/a.jpg]]
Or some other metadata on the target?
Bruce
https://orgmode.org/manual/Images.html
https://orgmode.org/manual/Internal-Links.html
next prev parent reply other threads:[~2021-08-11 11:54 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 [this message]
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
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-FPGOxYLKk+UkWVfoV75cCv_TZYeWDi25zxR60B9zdLorD2g@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).