From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Alan Tyree <alantyree@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: DEADLINE: position in entry
Date: Thu, 10 Nov 2016 16:08:34 +0100 [thread overview]
Message-ID: <87wpgbgyod.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAGMsgMwsxYDNo12rNd-xT_17dmwuO2m9FUF6NJVe8C5L-gHDjg@mail.gmail.com> (Alan Tyree's message of "Thu, 10 Nov 2016 10:59:49 +1100")
Hello,
Alan Tyree <alantyree@gmail.com> writes:
> Suggested wording:
>
> In 8.1:
>
>
> timestamp can appear anywhere in the headline or body of an Org tree
> entr UNLESS is is preceded by a keyword in which case it must be properly
> positioned or it will be ignored: see 8.3 for details.
This is wrong. Only the keyword is ignored, not the timestamp. This is
why DEADLINE and SCHEDULED location is unrelated to section 8.1.
> A timestamp may be preceded by special keywords to facilitate planning.
> WARNING: both the timestamp and the keyword are ignored if not positioned
> immediately following the headline. No space or other text is allowed.
I think "immediately following the headline" is unambiguous. No need to
specify "no space or other text is allowed".
I modified section 8.3 accordingly.
WDYT?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2016-11-10 15:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 9:37 DEADLINE: position in entry Alan Tyree
2016-11-09 14:20 ` Marco Wahl
2016-11-09 18:51 ` Philip Hudson
2016-11-09 20:42 ` Alan L Tyree
2016-11-09 23:36 ` Nicolas Goaziou
2016-11-09 23:44 ` Alan Tyree
2016-11-09 23:47 ` Samuel Wales
2016-11-09 23:59 ` Alan Tyree
2016-11-10 15:08 ` Nicolas Goaziou [this message]
2016-11-10 21:05 ` Alan Tyree
2016-11-11 0:12 ` Nicolas Goaziou
2016-11-11 1:52 ` Alan Tyree
2016-11-09 23:29 ` Nicolas Goaziou
2016-11-21 5:10 ` Yasushi SHOJI
2016-11-21 18:08 ` Sebastien Vauban
2016-11-23 8:09 ` Yasushi SHOJI
2016-11-25 11:24 ` Nicolas Goaziou
2016-11-29 7:54 ` Yasushi SHOJI
2016-11-29 8:35 ` Nicolas Goaziou
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wpgbgyod.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=alantyree@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
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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.