Re: [O] DEADLINE ignored?
Am 14.12.2017 um 16:39 schrieb Nicolas Goaziou: Rainer Stengele writes: 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? Definitely. Planning info is a single line, right below the heading. Most related code relies on that assumption. Regards, Thanks for clarifying, I will adjust and use multiple tasks. Regards Rainer
Re: [O] DEADLINE ignored?
Rainer Stengele writes: > 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? Definitely. Planning info is a single line, right below the heading. Most related code relies on that assumption. Regards,
Re: [O] DEADLINE ignored?
Am 14.12.2017 um 14:41 schrieb Nicolas Goaziou: Hello, Rainer Stengele 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
Re: [O] DEADLINE ignored?
Hello, Rainer Stengele 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, -- Nicolas Goaziou
Re: [O] DEADLINE ignored?
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 ..
Re: [O] DEADLINE ignored?
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. -- : Eric S Fraga via Emacs 26.0.50, Org release_9.0.10-723-g23eba9 signature.asc Description: PGP signature
[O] DEADLINE ignored?
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. 1) DEADLINE is identified and used. ** TODO Phone call DEADLINE: <2017-09-06 Wed> Maria's bill -> agenda capture:In 2 d.: TODO Phone call [<2017-09-06 Wed>] 2) DEADLINE is ignored ** TODO Phone call Maria's bill DEADLINE: <2017-09-06 Wed> -> agenda nothing 3) DEADLINE is ignored ** TODO Phone call DEADLINE: <2017-09-06 Wed> Maria's bill -> agenda nothing
