Ihor Radchenko writes:
> From 9b5f5844aedfab9f36ba89ed8beca36651370c0a Mon Sep 17 00:00:00 2001
> Message-Id:
> <9b5f5844aedfab9f36ba89ed8beca36651370c0a.1652099870.git.yanta...@gmail.com>
> From: Ihor Radchenko
> Date: Mon, 9 May 2022 20:34:38 +0800
> Subject: [PATCH] org-agenda-clock-report-h
Colin Baxter 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 h
> Ihor Radchenko writes:
> Colin Baxter writes:
>> Unfortunately, I see no difference in my clock tables whether I
>> have org-agenda-clock-report-header set to t, nil or something
>> like "My-Heading", or if I put :Header: as a tag in the file
>> headline that contains t
Colin Baxter writes:
> Unfortunately, I see no difference in my clock tables whether I have
> org-agenda-clock-report-header set to t, nil or something like
> "My-Heading", or if I put :Header: as a tag in the file headline that
> contains the clock table, or if I write :Header t in the #+BEGIN:
Hello Ihor,
> Ihor Radchenko writes:
> Colin Baxter writes:
>> Could more information perhaps be added to the doc string of
>> "org-agenda-clock-report-header"? And an example would be very
>> useful. As it stands at present, I haven't a clue as to what the
>> variable d
