emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Stephan Schmitt <drmabuse@cs.tu-berlin.de>
To: Christian Wittern <cwittern@gmail.com>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: PROPERTIES before the first headline
Date: Wed, 17 Feb 2010 15:01:58 +0100	[thread overview]
Message-ID: <4B7BF6D6.4030603@cs.tu-berlin.de> (raw)
In-Reply-To: <4B7B6EA2.7030606@gmail.com>

Hi Christian,

you forgot the colon after PROPERTY,
i.e. the following line at the beginning
of the buffer does work:

#+PROPERTY: myprop don't ask

(don't forget to refresh the buffer
setup by typing C-c C-c with the cursor
in that line).

Then the call

(org-entry-get (point) "myprop" t)

returns "don't ask".  Note the third
argument (t), which allows inheritance.

Hth,
	Stephan

Also sprach Christian Wittern:
> Hi there,
> 
> Extending my use of org-mode has left
> me running into another wall: I would
> like to set some custom properties
> globally for the whole file, before
> everything else.  There does not seem
> to be a way to do this
> 
> #+PROPERTY myprop don't ask
> 
> and having the :PROPERTY: drawer after
> the #+ lines also does not seem to
> work: Whenever I try to use the API
> functions to get at the property, I am
> told that I am before the first
> headling (which I know).  So, is this
> behavior intentional?  And if yes, is
> there a way to work around this?
> 
> All the best,
> 
> Christian
> 
> 
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

next prev parent reply	other threads:[~2010-02-17 14:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17  4:20 PROPERTIES before the first headline Christian Wittern
2010-02-17 14:01 ` Stephan Schmitt [this message]
2010-02-17 14:06   ` Stephan Schmitt
2010-02-17 14:28     ` Sebastian Rose
2010-02-17 14:29     ` Carsten Dominik
2010-02-18  1:50   ` Christian Wittern

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=4B7BF6D6.4030603@cs.tu-berlin.de \
    --to=drmabuse@cs.tu-berlin.de \
    --cc=cwittern@gmail.com \
    --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

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