From: Ihor Radchenko <yantar92@posteo.net>
To: Firmin Martin <firmin.martin@ens-lyon.fr>
Cc: emacs-orgmode@gnu.org
Subject: [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)])
Date: Sat, 22 Oct 2022 06:24:40 +0000 [thread overview]
Message-ID: <87pmek1il3.fsf@localhost> (raw)
In-Reply-To: <8735x04aqi.fsf@Inspiron.i-did-not-set--mail-host-address--so-tickle-me>
Firmin Martin <firmin.martin@ens-lyon.fr> writes:
> 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.
Sorry for the late reply.
Active timestamps are indeed not supported in clock lines. Only inactive
timestamps are currently allowed.
See https://orgmode.org/worg/dev/org-syntax.html#Clocks
Dear All,
Should we allow active timestamps in clocks? It sounds reasonable.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2022-10-22 6:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 16:07 Bug: Clock date range with the enclosing markup <> are not fully supported [9.4.4 (9.4.4-27-gb712b9-elpaplus)] Firmin Martin
2022-10-22 6:24 ` Ihor Radchenko [this message]
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=87pmek1il3.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=firmin.martin@ens-lyon.fr \
/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).