From: Eric Schulte <eric.schulte@gmx.com>
To: Ken Williams <Ken.Williams@windlogics.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: I'm tripping over #+BABEL: vs. #+PROPERTY:
Date: Wed, 14 Mar 2012 14:39:45 -0400 [thread overview]
Message-ID: <87aa3j2fim.fsf@gmx.com> (raw)
In-Reply-To: <21A5E1E970CD46459ECBE86D6CC4B28C5364FAE4@spexch01.WindLogics.local> (Ken Williams's message of "Wed, 14 Mar 2012 13:32:02 -0500")
> How about a translation of the text for question 2)?
[...]
>> > 2) In the same list of "Incompatible changes", it says "code blocks
>> > are named with - results are named with code block may still be
>> > labeled with named with #+tblname: will be considered to be named
>> > results". What on earth does that mean?? I would offer a doc patch
>> > but I can't figure it out. =)
Name code blocks with "#+name:" and their results will be named with
"#+results:", e.g.,
#+name: foo
#+begin_src emacs-lisp
:foo
#+end_src
#+RESULTS: foo
: :foo
If you want to include literal data you should also use "#+name:" to
name the data, e.g.,
#+name: bar
: bar
For backwards compatibility and inter-operation with existing table
functionality, you can use "#+tblname:" instead of "#+name:" when naming
a table.
#+tblname: baz
| foo | bar |
| baz | quz |
Hope that clarifies. Cheers,
--
Eric Schulte
http://cs.unm.edu/~eschulte/
next prev parent reply other threads:[~2012-03-14 18:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 18:23 I'm tripping over #+BABEL: vs. #+PROPERTY: Ken Williams
2012-03-14 18:28 ` Eric Schulte
2012-03-14 18:32 ` Ken Williams
2012-03-14 18:39 ` Eric Schulte [this message]
2012-03-14 18:49 ` Ken Williams
2012-03-14 21:21 ` Nick Dokos
2012-03-15 15:15 ` Sebastien Vauban
2012-03-15 16:14 ` Nick Dokos
2012-03-15 16:39 ` Thomas S. Dye
2012-03-18 21:37 ` Sebastien Vauban
2012-03-19 8:21 ` Rainer M Krug
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=87aa3j2fim.fsf@gmx.com \
--to=eric.schulte@gmx.com \
--cc=Ken.Williams@windlogics.com \
--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).