emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: David Masterson <dsmasterson@outlook.com>,
	"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Order of items after a headline in an Org outline?
Date: Sat, 09 Feb 2019 22:12:11 +0100	[thread overview]
Message-ID: <87zhr4mztg.fsf@aquinas.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <DM6PR07MB5532DE5FD52FA34358DF5C9CA56A0@DM6PR07MB5532.namprd07.prod.outlook.com>

Hi David,

David Masterson <dsmasterson@outlook.com> writes:

> Is there a documented requirement of the order of things in a Org
> outline?  

My understanding is that a lot of work in recent years has gone into
making Org's syntax more consistent, and this is an ongoing effort.  So,
sometimes things still work if they're not in the proper order, but I
wouldn't count on them remaining so.  Your best bet is just to use Org's
functions for inserting and modifying these things, e.g., org-schedule
to schedule something.

You might find this helpful:
https://orgmode.org/worg/dev/org-syntax.html

> For instance, do these things have to come directly after the
> headline and, if so, in what order?  Will Org get confused otherwise?

The correct order is:

> * SCHEDULED and DEADLINE
> * PROPERTY drawer

and then notes.  (Timestamps can occur anywhere within notes.)  e.g.:

--------------------------------------------------------------------------------

* Sample Headline
  DEADLINE: <2019-02-11 Mon> SCHEDULED: <2019-02-10 Sun>
  :PROPERTIES:
  :FOO:      bar
  :END:

Here I am typing some notes, late in the evening on [2019-02-09 Sat]

--------------------------------------------------------------------------------

Hope that helps!

-- 
Best,
Richard

  reply	other threads:[~2019-02-09 21:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-09 20:39 Order of items after a headline in an Org outline? David Masterson
2019-02-09 21:12 ` Richard Lawrence [this message]
2019-02-11 22:20   ` David Masterson
2019-02-09 21:22 ` Marco Wahl
2019-02-11 22:21   ` David Masterson
2019-02-10 12:31 ` Bernt Hansen

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=87zhr4mztg.fsf@aquinas.i-did-not-set--mail-host-address--so-tickle-me \
    --to=richard.lawrence@berkeley.edu \
    --cc=dsmasterson@outlook.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
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).