emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
* About the use of PROPERTY "meta lines"...
@ 2011-12-29  8:58 Sebastien Vauban
  2012-01-02 17:39 ` Eric Schulte
  0 siblings, 1 reply; 8+ messages in thread
From: Sebastien Vauban @ 2011-12-29  8:58 UTC (permalink / raw)
  To: emacs-orgmode-mXXj517/zsQ

#+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.

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

-- 
Sebastien Vauban

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2012-01-06 18:23 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-12-29  8:58 About the use of PROPERTY "meta lines" Sebastien Vauban
2012-01-02 17:39 ` Eric Schulte
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

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