emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Uwe Brauer <oub@mat.ucm.es>, emacs-orgmode@gnu.org
Subject: Re: org-clock-report on headings and subheadings or for the whole file?
Date: Sun, 13 Nov 2022 08:48:12 +0100	[thread overview]
Message-ID: <87sfine1mr.fsf@mat.ucm.es> (raw)
In-Reply-To: 87r0y7710r.fsf@localhost

[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]

> Uwe Brauer <oub@mat.ucm.es> writes:

> I had point before first heading and typed M-x org-clock-report.
> You probably had point at or inside a heading.

Correct, I did since I found it «logical» to have that table at the end of the file, but now I understand the problem with this. Thanks 

Ok, but I think it would not be bad to add this information to the docstring of org-clock-report!? It is not that intuitive.

BTW when I move one heading to a subheading the table reads 

#+BEGIN: clocktable :scope file :maxlevel 2
#+CAPTION: Clock summary at [2022-11-13 08:46]
| Headline             | Time   |      |
| *Total time*         | *2:33* |      |
| Symmetric            | 2:33   |      |
| \_  $A^0$ condition   |        | 0:03 |

Is there any way to avoid \   in the tanble

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. 

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]

  reply	other threads:[~2022-11-13  7:49 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
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 [this message]
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=87sfine1mr.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \


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