From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [babel] Loosing my latin...
Date: Thu, 24 Nov 2011 21:18:03 +0100 [thread overview]
Message-ID: <80pqgh2s1w.fsf@somewhere.org> (raw)
In-Reply-To: 30098.1322152077@alphaville.dokosmarshall.org
Hi Nick,
Nick Dokos wrote:
> Sebastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> wrote:
>> While this code block gets evaluated as expected [...]
>> It's not the same with the 2 following ones: variables `bar' and `baz' are
>> said to be void.
>>
>> ** NOK With property
>>
>> #+property: var bar=44
>> #+begin_src emacs-lisp
>> (+ bar bar)
>> #+end_src
>
> This one worked after C-c C-c on the property line.
I did C-c C-c on the property line -- before sending. It still does not work.
Even with the property line outside of the subtrees[1], that is at the top
level of the file, it still does not work after a C-c C-c...
>> ** NOK With headers
>>
>>
>> #+begin_src emacs-lisp
>> (+ baz baz)
>> #+end_src
>
> This one didn't - but it worked like this:
>
> #+headers: :var baz=55
Of course. Thanks for testing and reporting back!
The `:' is a must in front of the `var' keyword, in this case, as if it was on
the `#+begin' line.
> even with a singular "header" - doing this in a hurry, so I'm not sure
> if that's an accident of history left behind, or whether it would happen
> in a fresh session as well.
>> Am I missing something really obvious??[1]
It seems I did miss something quite obvious for the last case. Still unclear
why the second does not work for me.
Thanks for your time.
Best regards,
Seb
Footnotes:
[1] I fear what I did was not allowed. Though, it worked for you!?
--
Sebastien Vauban
next prev parent reply other threads:[~2011-11-24 20:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 15:42 [babel] Loosing my latin Sebastien Vauban
2011-11-24 16:27 ` Nick Dokos
2011-11-24 20:18 ` Sebastien Vauban [this message]
2011-11-25 7:33 ` 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=80pqgh2s1w.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).