Hi Russell, I see you are right. It seems that i have been going into strenuous lengths to brake orgmode manually, by splitting the DEADLINE / SCHEDULE properties on separate lines manually every time I am inserting a new item! After reverting them back to the first line only, it seems everything is working fine!
I agree though, that it might be beneficial to change this feature to use the PROPERTY drawers instead. Cheers, D. On Thu, 13 Aug 2020 at 18:47, Russell Adams <rlad...@adamsinfoserv.com> wrote: > On Thu, Aug 13, 2020 at 06:13:09PM +0100, Dinnyés Dániel wrote: > > Any response regarding this? Was this registered? If so, Is there a link > to > > track the bug status? > > Dinnyés, > > There is only the mailing list, there is no web based bug > tracker. These reports get attention as time permits. Developers > typically respond on the thread as that occurs. I'm just a helpful > guy. ;] > > More below regarding your issue. > > > > As stated earlier, the expected behaviour is that both leader/warning > > > texts are displayed on their appropriate line entry. > > I can reproduce your issue on Emacs 27.1 and Org 9.3.7, however it's > the documented behavior. The SCHEDULED and DEADLINE keywords must be > on the first line after the TODO item. They are not like a PROPERTY > block with dynamic placement within the block. > > Referring to the manual, > https://orgmode.org/manual/Deadlines-and-Scheduling.html > > #+begin_quote > 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. > #+end_quote > > Using C-c C-s (insert scheduled), and C-c C-d (insert deadline), Org > consistently appends them to the first line. > > How did your org file have them on separate lines? > > I agree that it may be slightly counter-intuitive to type manually, > but the tools provided add them correctly. > > If the behavior bothers you, I'm certain everyone would welcome a > patch. > > Finally, I've often wondered why Org hasn't migrated to using PROPERTY > drawers for all headline metadata. I suppose it's for legacy > compatibility. Perhaps you have an opinion there. I may start a thread > regarding that separately. > > My sample file: > > #+begin_src org > ,* TODO EXAMPLE sched first > SCHEDULED: <2020-08-13 Thu> > DEADLINE: <2020-08-13 Thu> > > ,* TODO EXAMPLE1 dead first > DEADLINE: <2020-08-13 Thu> > SCHEDULED: <2020-08-13 Thu> > > ,* TODO EXAMPLE2 dead first, 1 line > DEADLINE: <2020-08-13 Thu> SCHEDULED: <2020-08-13 Thu> > > ,* TODO EXAMPLE3 sched first, 1 line > SCHEDULED: <2020-08-13 Thu> DEADLINE: <2020-08-13 Thu> > > ,* TODO EXAMPLE w/ props, 1 line > SCHEDULED: <2020-08-13 Thu> DEADLINE: <2020-08-13 Thu> > :PROPERTIES: > :WUBBA: DUB DUB > :END: > #+end_src > > My sample agenda: > > #+begin_example > Week-agenda (W33): > Monday 10 August 2020 W33 > Tuesday 11 August 2020 > Wednesday 12 August 2020 > Thursday 13 August 2020 > test: Scheduled: TODO EXAMPLE sched first > test: Scheduled: TODO EXAMPLE2 dead first, 1 line > test: Scheduled: TODO EXAMPLE3 sched first, 1 line > test: Scheduled: TODO EXAMPLE w/ props, 1 line > test: Deadline: TODO EXAMPLE1 dead first > test: Deadline: TODO EXAMPLE2 dead first, 1 line > test: Deadline: TODO EXAMPLE3 sched first, 1 line > test: Deadline: TODO EXAMPLE w/ props, 1 line > test: TODO EXAMPLE sched first > test: TODO EXAMPLE1 dead first > Friday 14 August 2020 > Saturday 15 August 2020 > Sunday 16 August 2020 > #+end_example > > ------------------------------------------------------------------ > Russell Adams rlad...@adamsinfoserv.com > > PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ > > Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3 > >
