From: Alan Tyree <alantyree@gmail.com>
To: Alan Tyree <alantyree@gmail.com>,
Samuel Wales <samologist@gmail.com>,
emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: DEADLINE: position in entry
Date: Fri, 11 Nov 2016 08:05:29 +1100 [thread overview]
Message-ID: <CAGMsgMzOCQYQbmRVKWQahHYNPd-DhWhqLz++mgKziq5i6EjGDA@mail.gmail.com> (raw)
In-Reply-To: <87wpgbgyod.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1621 bytes --]
On 11 November 2016 at 02:08, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> 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.
>
Hi Nicolas,
Will you please double check this? On my system, the entry does *not* show
up in the agenda (C-c a a). If I remove the DEADLINE:, then it does show
up. So, for the important purpose under discussion, the timestamp is
ignored.
Emacs version 24.4.1 on Debian Stable
org-version: Org mode version 9.0 (9.0-elpaplus @
/home/alant/.emacs.d/elpa/org-plus-contrib-20161102/)
>
> > 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?
>
> Subject to the above, OK. Just so long as there is a good strong warning
about it.
Thanks,
Alan
Regards,
>
> --
> Nicolas Goaziou
>
--
Alan L Tyree http://austlii.edu.au/~alan
<http://www2.austlii.edu.au/%7Ealan>
Tel: 04 2748 6206 sip:typhoon@iptel.org
[-- Attachment #2: Type: text/html, Size: 2889 bytes --]
next prev parent reply other threads:[~2016-11-10 21:05 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
2016-11-10 21:05 ` Alan Tyree [this message]
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
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=CAGMsgMzOCQYQbmRVKWQahHYNPd-DhWhqLz++mgKziq5i6EjGDA@mail.gmail.com \
--to=alantyree@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@gmail.com \
/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).