emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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 07:43:16 +0000	[thread overview]
Message-ID: <87r0y7710r.fsf@localhost> (raw)
In-Reply-To: <87bkpbfhki.fsf@mat.ucm.es>

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

> I realized that I have 
> #+BEGIN: clocktable :scope subtree :maxlevel 2
> While you have
> #+BEGIN: clocktable :scope file :maxlevel 2
> But I don't know where shall I change the setting, the documentation of 
> ,----
> | org-clock-report (found in org-mode-map), which
> ...
> But I don't understand why org assumes that I call that function from a subtree.

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

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>

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


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