Bug#580893: arbtt: Add option to exclude categories
Joachim Breitner
mail at joachim-breitner.de
Sun May 9 20:56:20 CEST 2010
Hi,
Am Sonntag, den 09.05.2010, 13:35 -0400 schrieb Felipe Sateler:
> On Sun, May 9, 2010 at 12:40, Joachim Breitner <mail at joachim-breitner.de> wrote:
> > Should be easy to implement. I’m inclined to just extend --exclude to
> > support two kinds of invocations:
> > --exclude tag
> > or
> > --exclude category:
> >
> > This is in line with the new --intervals feature (not released yet) that
> > also takes either a tag or a category. Is that what you want?
>
>
> Not really sure about usefulness, but my first attempt at seeing if
> arbtt supported this was a glob pattern (Program:*). Perhaps someone
> can come up with a more interesting use for such a feature. I'm happy
> with being able to do -x category:
I implemented that now, and pushed it to the Darcs repository.
But I’m wondering if --exclude is really what you want. With --exclude,
you exclude *samples* from being taken into consideration, not the tags
from the output of the standard --total-time report. So
$ arbtt-stats --exclude Program:*
would give you statistics about the time where you were using no program
at all.
If you do want to filter the output, the exclude/include list for that
should be an option only relevant to the --total-time report. I have to
think of a good command line syntax for that.
Note that maybe a manual "grep -v" is enough to implement this,
following the good old Unix philosophy?
Anyways, you got me thinking if maybe the concept of “Category” could
actually be removed from the arbtt in a way that allows you to get the
feature youself in categorize.cfg. A new command for that file, maybe
"exclusive <tag-pattern>" would tell arbtt that it should make sure
there is at most one tag matching the pattern assigned to a sample. E.g.
"exclusive Program:*". The colon would have no special meaning to arbtt.
The asterisk can then be used in --exclude to exclude categories
(--exclude "Program:*") and other places.
This would allow for hierarchial tags as well. I could make Project:*
exclusive, and then have pie-chart-like-reports about
"Project:Debian:*".
The --every-category flag would be difficult to implement this way,
though.
But I’m not sure if it is worth the extra complexity on the user
interface level. Any opinions?
> > There is a mailinglist at http://lists.nomeata.de/mailman/listinfo/arbtt
> > that you might be interested in joining.
>
> Hmm, looks low traffic enough. I don't really subscribe to mailing
> lists, though. I prefer NNTP gateways. Is there one for this list?
I never worked with NNTP gateways... I guess I need an NNTP server for
that?
Greetings,
Joachim
--
Joachim "nomeata" Breitner
mail: mail at joachim-breitner.de | ICQ# 74513189 | GPG-Key: 4743206C
JID: nomeata at joachim-breitner.de | http://www.joachim-breitner.de/
Debian Developer: nomeata at debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <https://lists.nomeata.de/pipermail/arbtt/attachments/20100509/343388cb/attachment.asc>
More information about the arbtt
mailing list