From: Firmin Martin <firmin.martin@ens-lyon.fr>
To: emacs-orgmode@gnu.org
Subject: Bug: Clock date range with the enclosing markup <> are not fully supported [9.4.4 (9.4.4-27-gb712b9-elpaplus)]
Date: Fri, 12 Mar 2021 17:07:01 +0100 [thread overview]
Message-ID: <8735x04aqi.fsf@Inspiron.i-did-not-set--mail-host-address--so-tickle-me> (raw)
I have manually changed a clock date range in a task's logbook using the
shortcut =C-c .= (org-time-stamp). It modified the Org timestamp to the
date I wanted, but changed the enclosing markup from [] to <>. I didn't
pay much attention on it as C-c C-c (org-ctrl-c-ctrl-c) updated
correctly the total time.
But it happens that the change from [] to <> markup is enough to let
- clock table
- org-agenda-columns' CLOCKSUM_T property
completely ignore the clock entry I modified. I tested that after
changing the enclosing markup from <> to [], everything works as
expected. BTW, org-lint reports nothing on this.
Below is a minimal not working example.
1. In ~/test.org, put the following content.
* TODO Task
SCHEDULED:<2021-03-13 sam. ++1d>
:PROPERTIES:
:Effort: 1:00
:LAST_REPEAT: [2021-03-12 ven. 12:39]
:END:
:LOGBOOK:
- State "DONE" from "TODO" [2021-03-12 ven. 12:39]
CLOCK: <2021-03-12 ven. 09:15>--<2021-03-12 ven. 12:15> => 3:00
:END:
2. Insert the dynamic clock table and press C-c C-c on it
#+BEGIN: clocktable :scope ("~/test.org") :maxlevel 8 :block 2021-03-12
#+END:
the task does not show up.
3. Put this file in your agenda files and set agenda columns
(add-to-list org-agenda-files "~/test.org")
(setq org-columns-default-format-for-agenda "%50ITEM(Task) %2PRIORITY %10Effort(Effort){:} %10CLOCKSUM_T")
4. Now open org agenda in "columns mode"
(org-agenda-list)
(org-agenda-columns)
The task's CLOCKSUM_T field is empty.
5. Finally, replace the CLOCK property timestamp enclosing markup from <> to [] in
test.org. Try again 2. and 4.
Emacs : GNU Emacs 28.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.20, cairo version 1.16.0)
of 2021-01-20
Package: Org mode version 9.4.4 (9.4.4-27-gb712b9-elpaplus)
next reply other threads:[~2021-03-12 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 16:07 Firmin Martin [this message]
2022-10-22 6:24 ` [org-syntax] Should we support active timestamps in clock elements? (was: Bug: Clock date range with the enclosing markup <> are not fully supported [9.4.4 (9.4.4-27-gb712b9-elpaplus)]) Ihor Radchenko
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8735x04aqi.fsf@Inspiron.i-did-not-set--mail-host-address--so-tickle-me \
--to=firmin.martin@ens-lyon.fr \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).