From: Ihor Radchenko <yantar92@posteo.net>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-clock-report on headings and subheadings or for the whole file?
Date: Sun, 13 Nov 2022 05:01:02 +0000 [thread overview]
Message-ID: <8735an8n3l.fsf@localhost> (raw)
In-Reply-To: <87r0y8ha9g.fsf@mat.ucm.es>
Uwe Brauer <oub@mat.ucm.es> writes:
> I just started to use logbooks and clocks. One of my org files looks
> like this
>
> * TODO Condition about symmetry
> :LOGBOOK:
> CLOCK: [2022-11-11 16:40]--[2022-11-11 17:32] => 0:52
> CLOCK: [2022-11-11 13:58]--[2022-11-11 14:05] => 0:07
> CLOCK: [2022-11-11 11:22]--[2022-11-11 11:27] => 0:05
> CLOCK: [2022-11-11 09:55]--[2022-11-11 11:21] => 1:26
> :END:
>
>
> * TODO $A^0$ condition
> :LOGBOOK:
> CLOCK: [2022-11-11 17:40]--[2022-11-11 17:43] => 0:03
> :END:
>
> Now org-clock-report inserts a table for the lookbook of each heading.
>
>
> 1. Either I can make one of the heading a subheading, and then I
> would like to now how to make a report for heading and subheading.
>
> 2. Or I leave it as it is and want a report for every heading.
Could you please elaborate what you want to achieve?
I am getting
#+BEGIN: clocktable :scope file :maxlevel 2
#+CAPTION: Clock summary at [2022-11-13 Sun 12:58]
| Headline | Time |
|--------------------------+----------|
| *Total time* | *2h 33min* |
|--------------------------+----------|
| Condition about symmetry | 2h 30min |
| $A^0$ condition | 0h 3min |
#+END:
with Total time aggregating all the clock entries.
Isn't it what you want?
--
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>
next prev parent reply other threads:[~2022-11-13 5:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 8:01 org-clock-report on headings and subheadings or for the whole file? Uwe Brauer
2022-11-13 5:01 ` Ihor Radchenko [this message]
2022-11-13 7:08 ` Uwe Brauer
2022-11-13 7:18 ` Uwe Brauer
2022-11-13 7:43 ` Ihor Radchenko
2022-11-13 7:48 ` Uwe Brauer
2022-11-14 4:40 ` Ihor Radchenko
2022-11-14 7:10 ` Uwe Brauer
2022-11-15 1:38 ` Ihor Radchenko
2022-11-15 7:12 ` Uwe Brauer
2022-11-16 1:27 ` Ihor Radchenko
2022-11-14 7:15 ` Uwe Brauer
2022-11-15 1:40 ` Ihor Radchenko
2022-11-15 7:21 ` Uwe Brauer
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=8735an8n3l.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=oub@mat.ucm.es \
/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).