emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Re: Grouping clock report by tag?
Date: Sun, 06 Mar 2011 18:42:15 +0100	[thread overview]
Message-ID: <8762rwp2mg.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTi=TLfQ_pEW8wpchcvjicUfG5ws4fNO2u2hGt8vC@mail.gmail.com> (John Hendy's message of "Sun, 6 Mar 2011 11:02:30 -0600")

John Hendy <jw.hendy@gmail.com> writes:

> How about a clock table with a :tag: column and an option to sort by
> common tag? Again, I can already do something like this via the tag
> options, but I wouldn't mind all my clocked items appearing in one
>  table but sorted by tag. My tags = my projects/work area. It seems
> that a lot of people opt for the file desribing the project and thus
> the current table listing items by the file they appear in (or
> headline in the current file) probably works. I don't work like this,
> though. For me, tag sorting (even showing them) would be much more
> descriptive vs. trying to read the headlines and figure out what
> project it was.
> I could create a load of individual tables, so if this is a
> non-worthy request, I'll stick with creating a separate clock file
> that pulls together info from my agenda files and then create a
> spearate clock-table per tag.

Please provide an example with a clocktable..


  reply	other threads:[~2011-03-06 17:42 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 [this message]
     [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
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:

  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=8762rwp2mg.fsf@gnu.org \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=jw.hendy@gmail.com \


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