On 2025-06-29 21:32, Ihor Radchenko wrote:
pinmacs <pinm...@cas.cat> writes:
I am using this since February 2024 and for me it is very useful (see
attached script of just 17 lines).
The idea is to simplify two useful elements into one; when
(org-clock-in) is executed, org-timer is triggered.
Could you elaborate about the use cases when such timer is useful?
Use case 1: I usually try to work on my tasks with a timestamps saying
"in minute 5, I did this, in minute 10 I did that (...)", so that is
relevant and high detail on how the task went. Let me mask a real
example as attachment (in fact, this is from a task that end up sending
that email to share the script).
I took different approaches to solve a problem like this, and I am very
happy with the current solution.
Use case 2: when a meeting everyone agreed to have a recording, and you
want to note when other people talked, or put data on specific
timestamp; then, later, you can try to get to that timestamp in the
recording (there is a command to adjust the offset between the
recording/media and the time you start clocking, so it works very nice.
Use case 3: you are trying to solve an IT incident, and you want to
report what you did during the incident (later, a report might be
relevant to share)
For use case 2 and 3, you need to keep on the same clock ideally without
interruptions, and for use case 1, interruptions can happen. The script
works on these 3 use cases, etc.
That is a solution that integrates both things, org-clock to count time
on a task/project, and the follow-up within**** DONE worked on some stuff :tag1:tag2:
CLOSED: [2025-06-29 Sun 13:09] SCHEDULED: <2025-06-29 Sun 13:08>
:PROPERTIES:
:CREATED: [2025-06-29 Sun 10:16]
:CUSTOM_ID: 1activity_11988
:Effort: 0:20
:AS: [2025-06-29 Sun 10:16]
:clocking:
:AE: [2025-06-29 Sun 13:09]
:END:
:TRACE:
- State "DONE" from "DOIN" [2025-06-29 Sun 13:09]
- Rescheduled from "[2025-06-29 Sun 12:51]" on [2025-06-29 Sun 13:08]
- Rescheduled from "[2025-06-29 Sun 12:35]" on [2025-06-29 Sun 12:51]
- Rescheduled from "[2025-06-29 Sun 11:09]" on [2025-06-29 Sun 12:35]
- Rescheduled from "[2025-06-29 Sun 10:21]" on [2025-06-29 Sun 11:09]
- Rescheduled from "[2025-06-29 Sun 10:16]" on [2025-06-29 Sun 10:21]
- Rescheduled from "[2025-06-29 Sun]" on [2025-06-29 Sun 10:16]
:END:
:LOGBOOK:
CLOCK: [2025-06-29 Sun 13:08]--[2025-06-29 Sun 13:09] => 0:01
CLOCK: [2025-06-29 Sun 12:51]--[2025-06-29 Sun 13:07] => 0:16
CLOCK: [2025-06-29 Sun 12:35]--[2025-06-29 Sun 12:51] => 0:16
CLOCK: [2025-06-29 Sun 10:59]--[2025-06-29 Sun 12:27] => 1:28
CLOCK: [2025-06-29 Sun 10:21]--[2025-06-29 Sun 10:30] => 0:09
CLOCK: [2025-06-29 Sun 10:21]--[2025-06-29 Sun 10:21] => 0:00
CLOCK: [2025-06-29 Sun 10:16]--[2025-06-29 Sun 10:21] => 0:05
:END:
- 0:05:25 :: detail1
- 0:11:23 :: detail2
- 0:24:45 :: detail3
- 0:52:15 :: detail4
- 1:32:47 :: detail5
- 2:12:25 :: shared script with orgmode community
