jman writes:
> Why checking for dangling clocks in all files in `org-directory`?
Not in `org-directory', but all agenda files + all open Org buffers.
> .. Is it a common usecase to have clocks split in different files?
Yes, for some users.
> ... I'd like `org-clock-in` to close any running cl
I am a bit confused and I am probably missing some context.
The documentation of `org-clock-auto-clock-resolution` states: "When to
automatically resolve open clocks found in Org buffers." and the options are
"Never", "Always", "When no clock is running".
I think I understand the idea behind
I just tried to clock in to a task for the first time
in ... a while, and was immediately accosted with
hundreds of buffers being opened.
This seems to be because org-clock-in somehow
calls org-agenda or org-agenda-prepare or something
similar, however I cannot find the call site.
Is there a way
> This is because Org is checking if you have any dangling clocks present.
Seems like a reasonable default.
> See org-clock-auto-clock-resolution
Perfect solution for my case. Thanks!
Tom Gillespie writes:
> I just tried to clock in to a task for the first time
> in ... a while, and was immediately accosted with
> hundreds of buffers being opened.
This is because Org is checking if you have any dangling clocks present.
>
> Is there a way to disable this so that clocking does
