From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id mLfcBctoNl+hEAAA0tVLHw (envelope-from ) for ; Fri, 14 Aug 2020 10:34:51 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id IPHEActoNl+AdgAA1q6Kng (envelope-from ) for ; Fri, 14 Aug 2020 10:34:51 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 7F2EA94036A for ; Fri, 14 Aug 2020 10:34:50 +0000 (UTC) Received: from localhost ([::1]:59690 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k6X2v-00055q-9l for larch@yhetil.org; Fri, 14 Aug 2020 06:34:49 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:48646) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k6W2g-0000uo-2L for emacs-orgmode@gnu.org; Fri, 14 Aug 2020 05:30:30 -0400 Received: from mail-oi1-x22d.google.com ([2607:f8b0:4864:20::22d]:41970) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1k6W2c-0005Fr-C7 for emacs-orgmode@gnu.org; Fri, 14 Aug 2020 05:30:29 -0400 Received: by mail-oi1-x22d.google.com with SMTP id b22so7606615oic.8 for ; Fri, 14 Aug 2020 02:30:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=cN/aQwDER0d0wPOXkGGqdXEE47AwW1oXkeKLYdFD4x8=; b=TjjXlXGJTIS2ccivcazYzRxzK6g9EmwlTdiFjBWfrSIlzGuIEhGob1Dvxb9SNUIC1D jnEUWBxYSp9eOGZ9jeMLrId8dnOEn2Fz1dbUUkJIJG1viXodj5rko7BzjXjkY1/cgWcV fSWeDx7KXDEgswHqwaa8k4e+1LuTGVmG2P3g41qXbTiJHXSOzjEtvtlWCD6YyU5UEud8 zZ4k6EB9AIKfJWs7+Q9o5lwlum+fZIwFiZJYjCsnZzJo4L5DqpvB81DpIjYDUO2GwGQY DwF8/Zizm28taxFX8ZDu7CnR1z2yfuU7mwVuAuW0wOrwqXQ7ODItdxoR00Dxhs+jymkX Y7vA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=cN/aQwDER0d0wPOXkGGqdXEE47AwW1oXkeKLYdFD4x8=; b=ArZ5XV7xYHnQI8RY0tlmtNKSsdL/Mzy9QIuS+Q3Pungd8ugWGR5VcXMbFOugYujO9Q YqWgk3Mde3Jj8gvL0lbE2HT9ARQ9MVE+yNp5H2L/XRAy1uvBruRSxdvZrRORkSrJEqB0 KW40CwPbSaCojHO4LwYoZPYn3zWW7g4zMcT0gXCz34r2+1083QupzIXY+lhU1x5dqGEa ThQ6LbeGA7VoqfBUIHHTjG9f1j/AlPfB0kosL/BBYcNEZFppy0+VqBClCsfOZ/LIPl+m PlwjHxpLHFFN18xhrQWr9kxOwMnHkkTDjd9U0tyPztrZrjpvNKdc/UTGydyeGFZOOJHo 0KEQ== X-Gm-Message-State: AOAM533b2KzXGaaIxTBGT3zDy6Oj00Zs1CTJVzIAZO2Z2ADbvUoG8pj0 QdPREhtN8GrLl4rYUTem1mEAgM+gD+ufr1CO+a2oP3pN X-Google-Smtp-Source: ABdhPJxkl+dSV/r95RsnJnz8xk1JajpGbyJYyLA/hY1eAlUu+Ebk1Y8ANEXW75c9BlPOvq1+yMpbOBThcuAQOGy8eRs= X-Received: by 2002:a54:4383:: with SMTP id u3mr899588oiv.155.1597397424505; Fri, 14 Aug 2020 02:30:24 -0700 (PDT) MIME-Version: 1.0 References: <20200813174556.GA10871@maokai> In-Reply-To: <20200813174556.GA10871@maokai> From: =?UTF-8?B?RGlubnnDqXMgRMOhbmllbA==?= Date: Fri, 14 Aug 2020 10:29:48 +0100 Message-ID: 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/)] To: emacs-orgmode@gnu.org Content-Type: multipart/alternative; boundary="0000000000000d87e305acd3120a" Received-SPF: pass client-ip=2607:f8b0:4864:20::22d; envelope-from=dinnyesd@gmail.com; helo=mail-oi1-x22d.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=TjjXlXGJ; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Spam-Score: -1.71 X-TUID: uCC1mUSCUQot --0000000000000d87e305acd3120a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 wrote: > On Thu, Aug 13, 2020 at 06:13:09PM +0100, Dinny=C3=A9s D=C3=A1niel wrote: > > Any response regarding this? Was this registered? If so, Is there a lin= k > to > > track the bug status? > > Dinny=C3=A9s, > > 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 > > --0000000000000d87e305acd3120a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Russell,

I see you are ri= ght. It seems that i have been going into strenuous lengths to brake orgmod= e manually, by splitting the DEADLINE / SCHEDULE properties on separate lin= es 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 feat= ure to use the PROPERTY drawers instead.

Cheer= s,
D.



On Thu, 13 Aug 2020= at 18:47, Russell Adams <R= LAdams@adamsinfoserv.com> wrote:
On Thu, Aug 13, 2020 at 06:13:09PM +0100, Dinny=C3= =A9s D=C3=A1niel wrote:
> Any response regarding this? Was this registered? If so, Is there a li= nk to
> track the bug status?

Dinny=C3=A9s,

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/war= ning
> > 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-Sch= eduling.html

#+begin_quote
=C2=A0A timestamp may be preceded by special keywords to facilitate
=C2=A0planning. Both the timestamp and the keyword have to be positioned =C2=A0immediately 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 PROPE= RTY
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
=C2=A0 ,* TODO EXAMPLE sched first
=C2=A0 =C2=A0 SCHEDULED: <2020-08-13 Thu>
=C2=A0 =C2=A0 DEADLINE: <2020-08-13 Thu>

=C2=A0 ,* TODO EXAMPLE1 dead first
=C2=A0 =C2=A0 DEADLINE: <2020-08-13 Thu>
=C2=A0 =C2=A0 SCHEDULED: <2020-08-13 Thu>

=C2=A0 ,* TODO EXAMPLE2 dead first, 1 line
=C2=A0 DEADLINE: <2020-08-13 Thu> SCHEDULED: <2020-08-13 Thu>
=C2=A0 ,* TODO EXAMPLE3 sched first, 1 line
=C2=A0 SCHEDULED: <2020-08-13 Thu> DEADLINE: <2020-08-13 Thu>
=C2=A0 ,* TODO EXAMPLE w/ props, 1 line
=C2=A0 SCHEDULED: <2020-08-13 Thu> DEADLINE: <2020-08-13 Thu> =C2=A0 :PROPERTIES:
=C2=A0 :WUBBA:=C2=A0 =C2=A0 DUB DUB
=C2=A0 :END:
#+end_src

My sample agenda:

#+begin_example
=C2=A0 Week-agenda (W33):
=C2=A0 Monday=C2=A0 =C2=A0 =C2=A010 August 2020 W33
=C2=A0 Tuesday=C2=A0 =C2=A0 11 August 2020
=C2=A0 Wednesday=C2=A0 12 August 2020
=C2=A0 Thursday=C2=A0 =C2=A013 August 2020
=C2=A0 =C2=A0 test:=C2=A0 =C2=A0 =C2=A0 =C2=A0Scheduled:=C2=A0 TODO EXAMPLE= sched first
=C2=A0 =C2=A0 test:=C2=A0 =C2=A0 =C2=A0 =C2=A0Scheduled:=C2=A0 TODO EXAMPLE= 2 dead first, 1 line
=C2=A0 =C2=A0 test:=C2=A0 =C2=A0 =C2=A0 =C2=A0Scheduled:=C2=A0 TODO EXAMPLE= 3 sched first, 1 line
=C2=A0 =C2=A0 test:=C2=A0 =C2=A0 =C2=A0 =C2=A0Scheduled:=C2=A0 TODO EXAMPLE= w/ props, 1 line
=C2=A0 =C2=A0 test:=C2=A0 =C2=A0 =C2=A0 =C2=A0Deadline:=C2=A0 =C2=A0TODO EX= AMPLE1 dead first
=C2=A0 =C2=A0 test:=C2=A0 =C2=A0 =C2=A0 =C2=A0Deadline:=C2=A0 =C2=A0TODO EX= AMPLE2 dead first, 1 line
=C2=A0 =C2=A0 test:=C2=A0 =C2=A0 =C2=A0 =C2=A0Deadline:=C2=A0 =C2=A0TODO EX= AMPLE3 sched first, 1 line
=C2=A0 =C2=A0 test:=C2=A0 =C2=A0 =C2=A0 =C2=A0Deadline:=C2=A0 =C2=A0TODO EX= AMPLE w/ props, 1 line
=C2=A0 =C2=A0 test:=C2=A0 =C2=A0 =C2=A0 =C2=A0TODO EXAMPLE sched first
=C2=A0 =C2=A0 test:=C2=A0 =C2=A0 =C2=A0 =C2=A0TODO EXAMPLE1 dead first
=C2=A0 Friday=C2=A0 =C2=A0 =C2=A014 August 2020
=C2=A0 Saturday=C2=A0 =C2=A015 August 2020
=C2=A0 Sunday=C2=A0 =C2=A0 =C2=A016 August 2020
#+end_example

------------------------------------------------------------------
Russell Adams=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 RLAdams@AdamsInfoServ.com

PGP Key ID:=C2=A0 =C2=A0 =C2=A00x1160DCB3=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0http://www.adamsinfoserv.com/

Fingerprint:=C2=A0 =C2=A0 1723 D8CA 4280 1EC9 557F=C2=A0 66E8 1154 E018 116= 0 DCB3

--0000000000000d87e305acd3120a--