From: "Loris Bennett" <loris.bennett@fu-berlin.de>
To: emacs-orgmode@gnu.org
Subject: Re: Colon in block name?
Date: Fri, 13 Feb 2015 11:16:46 +0100 [thread overview]
Message-ID: <87sieayv3l.fsf@hornfels.zedat.fu-berlin.de> (raw)
In-Reply-To: 877fvmm89w.fsf@pinto.chemeng.ucl.ac.uk
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> On Friday, 13 Feb 2015 at 08:49, Loris Bennett wrote:
>
> [...]
>
>> In my ECM and in my original posting there are no empty lines between
>> the table information and the actual table (see attached screenshot of
>> my original ECM). However, I can see that in your quoted version above
>> there is one.
>
> Ummm, interesting. The way to avoid this issue may be to actually
> attach a file instead of pasting the contents into the email. Can you
> attach your ECM so that we can see what happens with it?
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: ecm --]
[-- Type: text/x-org, Size: 581 bytes --]
* 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.
[-- Attachment #3: Type: text/plain, Size: 53 bytes --]
--
This signature is currently under construction.
next prev parent reply other threads:[~2015-02-13 10:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 15:19 Colon in block name? Loris Bennett
2015-02-12 16:03 ` 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 [this message]
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=87sieayv3l.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).