From: Alan L Tyree <alantyree@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: DEADLINE: position in entry
Date: Thu, 10 Nov 2016 07:42:30 +1100 [thread overview]
Message-ID: <ccd9609a-a0bf-99a4-81f8-836dcbae7f6e@gmail.com> (raw)
In-Reply-To: <CAJ1MqVFTNFrAeyPQ_J=hrqOXUq4oNa5HbY7MitgxoZAFZp5mBw@mail.gmail.com>
On 10/11/16 05:51, Philip Hudson wrote:
> On 9 November 2016 at 14:20, Marco Wahl <marcowahlsoft@gmail.com> wrote:
>> In particular, no blank line is allowed between PLANNING and HEADLINE.
> I just checked, and was surprised to find that M-x org-lint RET does
> *not* catch this. Is this a bug in org-lint, or does org-lint not
> intend to catch this sort of thing?
>
>
Also, if this really is the case, then the manual needs to be modified.
Under 8.1, it says
" A timestamp can appear anywhere in the headline or body of an Org tree
entry."
and under 8.3:
"A timestamp may be preceded by special keywords to facilitate planning:"
I can't see anywhere that requires the DEADLINE: keyword to be flush
against a heading.
There may be some reason for requiring this, but if there is no good
reason, I would like to see it changed to be more flexible.
Alan
--
Alan L Tyree http://www2.austlii.edu.au/~alan
Tel: 04 2748 6206 sip:typhoon@iptel.org
next prev parent reply other threads:[~2016-11-09 20:42 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 [this message]
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
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=ccd9609a-a0bf-99a4-81f8-836dcbae7f6e@gmail.com \
--to=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.