From: Rainer Stengele <rainer.stengele@online.de>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Pdj <pauldj6@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: DEADLINE ignored?
Date: Thu, 14 Dec 2017 16:28:45 +0100 [thread overview]
Message-ID: <e820a565-c5df-0737-2599-95160e9fdb63@online.de> (raw)
In-Reply-To: <87fu8dv349.fsf@nicolasgoaziou.fr>
Am 14.12.2017 um 14:41 schrieb Nicolas Goaziou:
> Hello,
>
> Rainer Stengele <rainer.stengele@online.de> writes:
>
>> 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
>
> Sheer luck, I would say.
>
>> * 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?
>
> I cannot remember Org supporting this syntax, actually. I don't think
> anything 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>
>
> They do, but it's not new.
>
> Regards,
>
Thanks, Nicolas.
I am concerned hearing you say "sheer luck" because I am relying on such double entries, which seem to have worked well in the past:
* TODO [#A] Change tyres spring/autumn
DEADLINE: <2018-05-01 Di> SCHEDULED: <2018-04-21 Sa +1y>
DEADLINE: <2018-11-10 Sa> SCHEDULED: <2018-11-03 Sa +1y>
So is that working only by sheer luck?
Thank you.
Regards, Rainer
next prev parent reply other threads:[~2017-12-14 15:29 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
2017-12-14 13:41 ` Nicolas Goaziou
2017-12-14 15:28 ` Rainer Stengele [this message]
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=e820a565-c5df-0737-2599-95160e9fdb63@online.de \
--to=rainer.stengele@online.de \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--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.