From: "Loris Bennett" <loris.bennett@fu-berlin.de>
To: emacs-orgmode@gnu.org
Subject: Colon in block name?
Date: Thu, 12 Feb 2015 16:19:21 +0100 [thread overview]
Message-ID: <877fvnxime.fsf@hornfels.zedat.fu-berlin.de> (raw)
Hi,
I want to export to LaTeX and refer to tables and code blocks as in the
example below. However a name with a colon, such as 'tab:my_data' used
as a variable for a source block fails:
org-babel-ref-resolve: Reference 'my_data' not found in this buffer
Obviously, and perhaps not surprisingly, the use of the colon in the
name seems to be problematic.
Should this work? If not, is there a common alternative to the idiom
tab:shootings_in_the_foot and fig:foot_with_hole?
Cheers,
Loris
PS: In the example below, the last table is not exported to the LaTeX
file, but this is presumably an unrelated issue ...
Example:
* Test with block names containing a colon
** Data
My data can be found in Table [[tab:my_data]].
#+CAPTION: My data
#+NAME: tab:my_data
| a | b |
|---+---|
| 2 | 4 |
| 3 | 9 |
** Code
My code can be found in Listing [[code:my_code]].
#+CAPTION: My code
#+NAME: code:my_code
#+HEADER: :var data=tab:my_data :colnames yes
#+BEGIN_SRC R
d <- data
#+END_SRC
** Results
My results can be found in Table [[tab:my_results]].
#+CAPTION: My results
#+NAME: tab:my_results
#+RESULTS: code:my_code
| a | b |
|---+---|
| 2 | 4 |
| 3 | 9 |
** Conclusions
Names with colons don't work.
--
This signature is currently under construction.
next reply other threads:[~2015-02-12 15:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 15:19 Loris Bennett [this message]
2015-02-12 16:03 ` Colon in block name? Eric S Fraga
2015-02-13 7:49 ` Loris Bennett
2015-02-13 10:10 ` Eric S Fraga
2015-02-13 10:16 ` Loris Bennett
2015-02-13 10:34 ` Loris Bennett
2015-02-13 11:18 ` Stefan Nobis
2015-02-13 12:36 ` Loris Bennett
2015-02-13 18:43 ` Eric S Fraga
2015-04-11 16:14 ` Nicolas Goaziou
2015-04-15 9:02 ` Loris Bennett
2015-02-13 19:11 ` Nick Dokos
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=877fvnxime.fsf@hornfels.zedat.fu-berlin.de \
--to=loris.bennett@fu-berlin.de \
--cc=emacs-orgmode@gnu.org \
/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).