emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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:28:53 -0400	[thread overview]
Message-ID: <87ipi72g0q.fsf@gmx.com> (raw)
In-Reply-To: <21A5E1E970CD46459ECBE86D6CC4B28C5364FAE0@spexch01.WindLogics.local> (Ken Williams's message of "Wed, 14 Mar 2012 13:23:40 -0500")

Hi Ken,

Did you press C-c C-c on each property line after it was written?
Property lines only take effect either with C-c C-c, or when the file is
first opened.


Ken Williams <Ken.Williams@windlogics.com> writes:

> 1) I see from http://orgmode.org/Changes.html, section "Incompatible
> changes", that I have to change my #+BABEL: lines to something else,
> in order to upgrade from 7.7 to 7.8.03.  But I can't figure out to
> what.
> I previously had:
> #+BABEL: :session *R* :results output :exports both
> #+begin_src R :exports none :results silent
> setwd('c:/Users/ken/wdir')
> source("src/main/R/mylib.R")
> #+end_src
> What does that translate to, using #+PROPERTY: syntax?  I tried the
> following, but then when I execute a "#+begin_src R" block, it doesn't
> evaluate in a session called *R*, it just evaluates in-process.  No
> *R* buffer is created.
> #+PROPERTY: session *R*
> #+PROPERTY: results output
> #+PROPERTY: exports both
> A pointer to some transition doc would also be great, if such a thing exists.
> 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. =)
> --
> Ken Williams, Senior Research Scientist
> WindLogics
> http://windlogics.com
> CONFIDENTIALITY NOTICE: This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of any kind is strictly prohibited. If you are not the intended recipient, please contact the sender via reply e-mail and destroy all copies of the original message. Thank you.

Eric Schulte

  reply	other threads:[~2012-03-14 18:29 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 [this message]
2012-03-14 18:32   ` Ken Williams
2012-03-14 18:39     ` Eric Schulte
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:

  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=87ipi72g0q.fsf@gmx.com \
    --to=eric.schulte@gmx.com \
    --cc=Ken.Williams@windlogics.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).