emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: cberry@tajo.ucsd.edu
To: emacs-orgmode@gnu.org
Subject: Re: [babel]  PROPERTY doesn't do what BABEL did
Date: Wed, 14 Dec 2011 20:32:37 -0800	[thread overview]
Message-ID: <87iplifo9m.fsf@tajo.ucsd.edu> (raw)
In-Reply-To: 87k45yy6wr.fsf@gmx.com

Eric Schulte <eric.schulte@gmx.com> writes:

> cberry@tajo.ucsd.edu writes:
>
>> I would like to get the same behavior as when I export a file with (say)
>> these three lines:
>>
>> #+begin_src emacs-lisp :var foo=1 :var bar=2 :results value :exports both
>>   (+ foo bar)
>> #+end_src
>>
>> But I'd like to set a buffer wide PROPERTY to achieve that as with a
>> file with these lines:
>>
>> #+property: var  foo=1
>> #+property: var+ bar=2
>> #+begin_src emacs-lisp :results value :exports both
>> (+ foo bar)
>> #+end_src
>>
>
> The above works on my system.  You may want to try C-c C-c on one of the
> property lines so that Org-mode re-reads them (it does this
> automatically upon opening an Org-mode file).


Eric,

That did it. 

So when editting #+PROPERTY lines, C-c C-c on one of them to update the
settings.

I see this documented in org-ctrl-c-ctrl-c now.

But I missed it in the manual.

Thanks,

Chuck

>
> Best,
>
>>
>> it throws an error under 7.8.02 (downloaded as tar.gz) when I try to
>> export it with 'C-c C-e a yes RET' :
>>
>>           progn: Symbol's value as variable is void: foo
>>
>> Other trials seem to show that #+PROPERTY: is ignored by the src blocks
>>
>> I'd really like to get something that does what BABEL used to do as I
>> have a lot of code that relies on that behavior. :-(
>>
>> Chuck
>>
>> ---
>>
>>

      reply	other threads:[~2011-12-15  4:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-14 23:04 [babel] PROPERTY doesn't do what BABEL did cberry
2011-12-15  1:12 ` Eric Schulte
2011-12-15  4:32   ` cberry [this message]

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=87iplifo9m.fsf@tajo.ucsd.edu \
    --to=cberry@tajo.ucsd.edu \
    --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).