On Jul 23, 2009, at 12:10 AM, meingbg wrote:
When using the :step day option in the clocktable, every day gets
it's own table. This is a great option! It can however easily be a
lot of tables, even if there's not too much information. Say for
example there are only items in two out of thir
meingbg writes:
> And while I'm at it - my employer requires me to report not only what I'm
> doing
> and how long it takes, but also when I'm doing it. I assume most people
> wouldn't benefit from a feature like this, and that there are many other
> things
> on the wish list with higher priori
meingbg writes:
> Just looking at the output, maybe this could be implemented as a regexp
> replace
> on the entire block performed after putting together the tables? Just thinking
> it might save you some headache, if you don't think it's too ugly of a hack.
Well, it *is* to ugly of a hack, bu
Thank you, this one would save my eyes a bit!
Just looking at the output, maybe this could be implemented as a regexp
replace on the entire block performed after putting together the tables?
Just thinking it might save you some headache, if you don't think it's too
ugly of a hack.
And while I'm a
meingbg writes:
> When using the :step day option in the clocktable, every day gets it's own
> table. This is a great option! It can however easily be a lot of tables, even
> if there's not too much information. Say for example there are only items in
> two out of thirty tables.
>
> Is there an o
