From: Ihor Radchenko <yantar92@posteo.net>
To: Sau P <sau@yaaama.xyz>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] org clock wants to resolve clocks every time a clock in, occurs [9.7 (9.7-??-0dd2c5e @, /home/aayush/.config/emacs/.local/straight/build-29.2/org/)]
Date: Sat, 24 Feb 2024 17:41:18 +0000 [thread overview]
Message-ID: <87bk85wyip.fsf@localhost> (raw)
In-Reply-To: <ff425d64-2059-4ecd-9f0d-34ba839509ed@yaaama.xyz>
Sau P <sau@yaaama.xyz> writes:
> What should happen?
> When I clock in, the clock should continue
> until I clock out (or go idle).
>
> What actually happens?
> Every minute I will get a popup requesting me to resolve a clock.
>
> This has been happening for a number of days now and I thought I had
> dangling clocks but I don't think this is the case.
> Even after "resolving" the clock (I have exhausted every option the
> popup gives), the resolve popup comes back a minute later.
Sounds like your `org-clock-idle-time' is customized to a small number
(1 minute).
> I believe I have seen someone with a similar issue on stackexchange,
> here is the link:
> https://emacs.stackexchange.com/questions/70084/resolving-idle-time-after-forced-closing-crash
That sounds different and that is not a bug - org-clock-out does not
trigger clock resolution. Only attempting to clock-in will do it.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2024-02-24 17:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 2:11 [BUG] org clock wants to resolve clocks every time a clock in, occurs [9.7 (9.7-??-0dd2c5e @, /home/aayush/.config/emacs/.local/straight/build-29.2/org/)] Sau P
2024-02-24 17:41 ` Ihor Radchenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bk85wyip.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=sau@yaaama.xyz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).