emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-orgmode@gnu.org
Subject: org-clock-report on headings and subheadings or for the whole file?
Date: Sat, 12 Nov 2022 09:01:15 +0100	[thread overview]
Message-ID: <87r0y8ha9g.fsf@mat.ucm.es> (raw)


I just started to use logbooks and clocks. One of my org files looks
like this

* TODO Condition about symmetry  
  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

* TODO $A^0$ condition
  CLOCK: [2022-11-11 17:40]--[2022-11-11 17:43] =>  0:03

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.

I am aware  of 

But prefer not to touch the structure of the file.

Any idea how to insert a table for all logbooks? 

Thanks and regards

Uwe Brauer

Warning: Content may be disturbing to some audiences
I strongly condemn Putin's war of aggression against the Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the ban of Russia from SWIFT.
I support the EU membership of the Ukraine. 

             reply	other threads:[~2022-11-12  8:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-12  8:01 Uwe Brauer [this message]
2022-11-13  5:01 ` org-clock-report on headings and subheadings or for the whole file? Ihor Radchenko
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:

  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=87r0y8ha9g.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --cc=emacs-orgmode@gnu.org \


* 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


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).