From: Ihor Radchenko <yantar92@gmail.com>
To: Colin Baxter <m43cap@yandex.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Re: org-agenda-clock-report-header
Date: Thu, 12 May 2022 17:40:30 +0800 [thread overview]
Message-ID: <87fslfhywh.fsf@localhost> (raw)
In-Reply-To: <87ilqbgmu9.fsf@yandex.com>
Colin Baxter <m43cap@yandex.com> writes:
> > Because your clock tables in Org _files_ have nothing to do with
> > agenda. There is no "Agenda clock report mode" when you create an
> > ordinary clock report in Org buffers.
>
> Well now you've really confused me because I wasn't in an agenda buffer,
> I had constructed a clock table from a non-agenda org file.
>
> Could give me a concrete example of where the variable
> org-agenda-clock-report-header might be used?
When you are in agenda, you can press v R to toggle
org-agenda-clockreport-mode:
(11.5 Commands in the Agenda Buffer)
>> Toggle Clockreport mode. In Clockreport mode, the daily/weekly
>> agenda always shows a table with the clocked times for the time
>> span and file scope covered by the current agenda view. The
>> initial setting for this mode in new agenda buffers can be set with
>> the variable ‘org-agenda-start-with-clockreport-mode’. By using a
>> prefix argument when toggling this mode (i.e., ‘C-u R’), the clock
>> table does not show contributions from entries that are hidden by
>> agenda filtering(1). See also the variable
>> ‘org-clock-report-include-clocking-task’.
Best,
Ihor
next prev parent reply other threads:[~2022-05-12 10:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 17:03 org-agenda-clock-report-header Colin Baxter
2022-05-09 12:38 ` [PATCH] org-agenda-clock-report-header Ihor Radchenko
2022-05-09 18:07 ` Colin Baxter
2022-05-11 11:46 ` Ihor Radchenko
2022-05-12 8:46 ` Colin Baxter
2022-05-12 9:40 ` Ihor Radchenko [this message]
2022-07-17 9:09 ` Ihor Radchenko
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=87fslfhywh.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=m43cap@yandex.com \
/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).