From: Eric Schulte <eric.schulte@gmx.com>
To: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: About the use of PROPERTY "meta lines"...
Date: Mon, 02 Jan 2012 10:39:53 -0700 [thread overview]
Message-ID: <871uridlb1.fsf@gmx.com> (raw)
In-Reply-To: 807h1fycsm.fsf@somewhere.org
"Sebastien Vauban" <wxhgmqzgwmuf@spammotel.com> writes:
> #+TITLE: Properties
> #+AUTHOR: Seb Vauban
> #+PROPERTY: var foo=1
> #+PROPERTY: var+ bar=2
>
> * Abstract
>
> IIUC, properties are set in this way:
>
> - on a file basis, before any heading, through the =PROPERTY= keyword,
> - on a subtree basis, through the =PROPERTIES= block.
>
> My comprehension is that the =PROPERTY= keyword may not be used inside "trees",
> and should be ignored if that would happen.
>
While it is not normal usage, I think that it is legal for #+PROPERTY:
lines (or #+Option: lines etc...) to appear inside of subtrees.
Best -- Eric
>
> The following example shows that either:
>
> - I'm wrong to think so,
> - there is a bug.
>
> What is the right assumption here?
>
> * Subtree
>
> Being located in a subtree, the following lines are ill-placed IMHO:
>
> #+PROPERTY: var foo="Hello
> #+PROPERTY: var+ world"
>
> Though, they're well taken into account:
>
> #+begin_src emacs-lisp
> foo
> #+end_src
>
> #+results:
> : Hello world
>
> These lines have even wiped the definition of =bar= (because of the use of =var=
> without any =+=):
>
> #+begin_src emacs-lisp
> (+ foo bar)
> #+end_src
>
> returns the error "Symbol's value as variable is void: bar."
>
> Best regards,
> Seb
--
Eric Schulte
http://cs.unm.edu/~eschulte/
next prev parent reply other threads:[~2012-01-02 18:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 8:58 About the use of PROPERTY "meta lines" Sebastien Vauban
2012-01-02 17:39 ` Eric Schulte [this message]
2012-01-03 7:42 ` Sebastien Vauban
2012-01-06 7:28 ` Eric Schulte
2012-01-06 7:57 ` Torsten Wagner
2012-01-06 17:13 ` cberry
2012-01-06 18:22 ` Eric Schulte
2012-01-06 18:07 ` Eric Schulte
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=871uridlb1.fsf@gmx.com \
--to=eric.schulte@gmx.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.com \
/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).