From: Russell Adams <RLAdams@AdamsInfoServ.Com>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: org agenda leader text "on-the-date" doesn't show for items with both SCHEDULED and DEADLINE properties [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.1/lisp/org/)]
Date: Thu, 13 Aug 2020 19:45:56 +0200 [thread overview]
Message-ID: <20200813174556.GA10871@maokai> (raw)
In-Reply-To: <CAFfHKJ5XdAgtEfHKSAuiR5Wp2hRaMiOvPENK8UMHMhBtO7Wk3Q@mail.gmail.com>
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 RLAdams@AdamsInfoServ.com
PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/
Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
next prev parent reply other threads:[~2020-08-13 17:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 9:48 Bug: org agenda leader text "on-the-date" doesn't show for items with both SCHEDULED and DEADLINE properties [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.1/lisp/org/)] Dinnyés Dániel
2020-08-13 17:13 ` Dinnyés Dániel
2020-08-13 17:45 ` Russell Adams [this message]
2020-08-14 1:19 ` Kyle Meyer
2020-08-14 9:29 ` Dinnyés Dániel
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=20200813174556.GA10871@maokai \
--to=rladams@adamsinfoserv.com \
--cc=emacs-orgmode@gnu.org \
/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.