From: John Hendy <jw.hendy@gmail.com>
To: Bernt Hansen <bernt@norang.ca>
Cc: Bastien <bzg@altern.org>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [Orgmode] Grouping clock report by tag?
Date: Fri, 6 May 2011 15:30:12 -0500 [thread overview]
Message-ID: <BANLkTi=-de-wwrPVEe6ZaThVoC0Fvtgp7Q@mail.gmail.com> (raw)
In-Reply-To: <87pqnw7nk3.fsf@norang.ca>
On Thu, May 5, 2011 at 6:08 PM, Bernt Hansen <bernt@norang.ca> wrote:
> John Hendy <jw.hendy@gmail.com> writes:
>
>> Following up on this again... It's been almost 2mos. Is there any way
>> to add a tag grouping to clock reports rather than needing to create
>> clock reports for every tag?
>>
>> Many thanks,
>> John
>>
>> My initial example:
>> ----
>> A rough idea might be like this:
>>
>> -----------
>>
>> #+BEGIN: clocktable :maxlevel 2 :scope agenda
>> Clock summary at [2011-03-06 Sun 17:59]
>> | Tag | Headline | Time | | File |
>> |------+------------------+---------+------+----------------|
>> | | ALL *Total time* | *10:00* | | |
>> |------+------------------+---------+------+----------------|
>> | Tag1 | *Tag time* | *5:00* | | |
>> | | [2011-02-04 Fri] | 3:30 | | 2011-02Feb.org |
>> | | Some task | | 3:30 | |
>> | | [2011-01-21 Fri] | 0:30 | | 2011-01Jan.org |
>> | | Some task | | 0:30 | |
>> | | [2010-12-09 Thu] | 1:00 | | 2010-12Dec.org |
>> | | Some task | | 1:00 | |
>> |------+------------------+---------+------+----------------|
>> | Tag2 | *Tag time* | *5:00* | | |
>> | | [2011-02-04 Fri] | 3:30 | | 2011-02Feb.org |
>> | | Some task | | 3:30 | |
>> | | [2011-01-21 Fri] | 0:30 | | 2011-01Jan.org |
>> | | Some task | | 0:30 | |
>> | | [2010-12-09 Thu] | 1:00 | | 2010-12Dec.org |
>> | | Some task | | 1:00 | |
>> |------+------------------+---------+------+----------------|
>> -----
>
> Hi John,
>
> Niels Giesen posted some patches for summarizing clock reports by
> arbitrary properties. Maybe this will be useful?
>
> http://thread.gmane.org/gmane.emacs.orgmode/40160
>
> I'm not aware of any functionality that does what you describe above.
>
His is actually pretty darn close. It looks like Carsten just
re-requested a patch in some standard format a few days ago, so
perhaps I can hold my breath for it to get applied. Otherwise, do I
just copy/paste his code into manual files and then do something like
'patch -p0 file.patch'?
And will it get overrun by my next pull?
Sorry... never applied a patch to org-mode files.
John
> Regards,
> Bernt
>
next prev parent reply other threads:[~2011-05-06 20:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 0:25 Grouping clock report by tag? John Hendy
2011-03-06 13:20 ` Bastien
2011-03-06 17:02 ` John Hendy
2011-03-06 17:42 ` Bastien
[not found] ` <AANLkTim6kxpDVxXw5krSbpDK+x3=wfB2iqN6g9nWujx2@mail.gmail.com>
2011-03-06 18:08 ` John Hendy
2011-03-07 10:11 ` Giovanni Ridolfi
2011-03-11 22:06 ` John Hendy
2011-05-05 19:33 ` [Orgmode] " John Hendy
2011-05-05 23:08 ` Bernt Hansen
2011-05-06 20:30 ` John Hendy [this message]
2011-05-06 23:55 ` Bernt Hansen
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='BANLkTi=-de-wwrPVEe6ZaThVoC0Fvtgp7Q@mail.gmail.com' \
--to=jw.hendy@gmail.com \
--cc=bernt@norang.ca \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
/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).