On 7/10/22, Ihor Radchenko wrote:
> Every agenda line, which corresponds to a headline contains a non-nil
> 'org-hd-marker text property. In log mode, there will also be non-nil
> 'date and 'time-of-day text properties. You can examine the full list
idk if this is helpful but at one point long ag
I also use org-mode clocking to record time spent.
But instead of modifying/configuring org-mode, I use a post-processing
Python script to collect and summarize clocked times.
locale.setlocale(locale.LC_ALL, '')
# ...
def extract_times(line):
# CLOCK: [-mm-dd WKD HH:MM]--[
Russell Adams writes:
>> Can you then formulate what exactly you want to achieve?
>> Do you want to consider only agenda items? All the timestamps in the
>> matching items or maybe just some?
>
> I typically use agenda for the month with logbook view and inactive
> timestamps enabled.
>
> I'd lov
On Sat, Jul 09, 2022 at 12:00:53PM +0800, Ihor Radchenko wrote:
> Russell Adams writes:
>
> > I just want to get the agenda items in a programmatic way so I can
> > report on them.
>
> Can you then formulate what exactly you want to achieve?
> Do you want to consider only agenda items? All the tim
Russell Adams writes:
> I just want to get the agenda items in a programmatic way so I can
> report on them.
Can you then formulate what exactly you want to achieve?
Do you want to consider only agenda items? All the timestamps in the
matching items or maybe just some?
Best,
Ihor
On Fri, Jul 08, 2022 at 03:02:00PM +0800, Ihor Radchenko wrote:
> You may hook into timestamp insertion/todo-state change functions and
> accumulate the "time" into headline properties.
Hooking on insertion is a bit low level, and sounds like it's only
about maintaining state in the currently runn
Russell Adams writes:
> I find Org's clocking to be too detailed, and that it doesn't play
> well with dynamically organized hierarchies of notes. I frequently
> create and close subtasks, or switch parts of the tree. Clocking each
> one is too much overhead, and too granular. I don't need to pro
make list of (ts . header) pairs [at least bare ia], rounding all tses
to hour, sort -u by ts, seq-group-by on ts to get (hour. headers)? or
do i not get it?
On 6/30/22, Russell Adams wrote:
> On Wed, Jun 29, 2022 at 07:11:10PM -0700, Samuel Wales wrote:
> I appreciate that! That's really what I
On Wed, Jun 29, 2022 at 07:11:10PM -0700, Samuel Wales wrote:
> a few things taht are probably all completely obvious or investigated
> or irrelevant just in case. just brainstorm.
I appreciate that! That's really what I'm asking for is ideas. I don't
mind writing a bit of code, but I'm not sure
i said clocked notation, but i meant closed notation. clocked
notation, i am not sure of.
On 6/29/22, Samuel Wales wrote:
> a few things taht are probably all completely obvious or investigated
> or irrelevant just in case. just brainstorm.
>
> do you have everything relevant in the same subtre
a few things taht are probably all completely obvious or investigated
or irrelevant just in case. just brainstorm.
do you have everything relevant in the same subtrees? i.e. not
wanting granular, can you search upward for a dominating entry kind of
like git searching upward for the .git dir or s
On Thu, Jun 30, 2022 at 07:26:20AM +1000, Tim Cross wrote:
> > The point is that I'm not worried about accounting time by task,
> > instead I'm aggregating tasks into accounting by whole hours.
> >
> > I'm looking at org-element, and it appears I'd have to do my own
> > agenda style scan of the who
Russell Adams writes:
> I make extensive use of timestamps for billing (timesheet)
> purposes. I'm looking to automate this more, and I find the existing
> clocking system inadequate. I'm hoping someone can point me in the
> right direction.
>
> Today I have log mode enabled so that each time I
13 matches
Mail list logo