From: Rainer Stengele <rainer.stengele@online.de>
To: Pdj <pauldj6@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: DEADLINE ignored?
Date: Thu, 14 Dec 2017 11:59:24 +0100 [thread overview]
Message-ID: <813df7d1-1275-97c8-6f72-200b99f99b1b@online.de> (raw)
In-Reply-To: <87fuc2ahmn.fsf@pinto.chemeng.ucl.ac.uk>
Am 04.09.2017 um 12:21 schrieb Eric S Fraga:
> On Monday, 4 Sep 2017 at 12:08, Pdj wrote:
>> Hello, I am observing this (funky?) behavior:
>> in the agenda, the deadline seems to be identified only if it
>> immediately follows the headline, and it is ignored otherwise.
>> Am I missing something? Thank you, Paolo.
>
> You are not missing something. As the manual says:
>
> A timestamp may be preceded by special keywords to facilitate
> planning. Both the timestamp and the keyword have to be positioned
> immediately after the task they refer to.
>
> I guess immediately means not even a blank line.
>
Hi,
it looks like
* TODO task
DEADLINE: <2017-12-14 Do>
SCHEDULED: <2017-12-14 Do>
will find the DEADLINE and SCHEDULE timestamp and display correctly in the agenda while
* TODO task
SCHEDULED: <2017-12-14 Do>
DEADLINE: <2017-12-14 Do>
will still find the SCHEDULED tinestamp but no more the DEADLINE.
I had this sequence in my org templates in the past and had no issues as far as I remember.
Has this behaviour changed?
Freshly creating a new SCHEDULED and DEADLINED timestamp results in the structure below.
Do all tasks now need to have both items in the same line like here:
* TODO task
SCHEDULED: <2017-12-14 Do> DEADLINE: <2017-12-14 Do>
Thank you.
Regards, Rainer
Org mode version 9.1.4 (release_9.1.4-206-g4b80c6.dirty ..
next prev parent reply other threads:[~2017-12-14 10:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 10:08 DEADLINE ignored? Pdj
2017-09-04 10:21 ` Eric S Fraga
2017-12-14 10:59 ` Rainer Stengele [this message]
2017-12-14 13:41 ` Nicolas Goaziou
2017-12-14 15:28 ` Rainer Stengele
2017-12-14 15:39 ` Nicolas Goaziou
2017-12-14 22:06 ` Rainer Stengele
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=813df7d1-1275-97c8-6f72-200b99f99b1b@online.de \
--to=rainer.stengele@online.de \
--cc=emacs-orgmode@gnu.org \
--cc=pauldj6@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 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.