From: Rens Oliemans <hallo@rensoliemans.nl>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Capital-letter options from dangling clock don't clock out [9.8-pre (release_9.7.7-106-g114c76 @ /home/rens/Projects/org/org-mode/lisp/)]
Date: Wed, 24 Jul 2024 13:31:57 +0200 [thread overview]
Message-ID: <87bk2njaaa.fsf@rensoliemans.nl> (raw)
In-Reply-To: <87a5i7dr2f.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]
Ihor Radchenko <yantar92@posteo.net> writes:
> May you please provide more details?
> What exactly did you try to do, step by step?
I clocked in ('org-clock-in') in a headline with a dangling clock. I got the Clock
Resolution popup menu, and pressed an uppercase letter, which according to the popup menu
should leave me clocked out:
For all these options, using uppercase makes your final state to be CLOCKED OUT.
I know that I clocked /in/, and that it might make sense to end up clocked in, but if that
is the case I think that the popup menu is very misleading and might be improved. In fact,
if that is the case, I believe that there is no difference in the lowercase and uppercase
options at all.
In that case, please let me know how I'm mistaken and I am happy to try to improve the
popup menu text to clarify this.
See the attached org document for detailed instructions:
[-- Attachment #2: test.org --]
[-- Type: application/vnd.lotus-organizer, Size: 1046 bytes --]
[-- Attachment #3: Type: text/plain, Size: 577 bytes --]
The reason why I clock in and expect to end up clocked out (albeit with the Clock
Resolution) is perhaps a bit strange. I do this because I sync my Org files between my
computers, and this leaves me with a dangling clock once in a while. Clocking out to fix
this doesn't work ("No active clock"), and the way I fix this is by clocking in, since the
Clock Resolution Command is very helpful in fixing idle minutes. Then, I cancel the
current clock so that I end up clocked-out. However, the wording of the popup menu
suggests that the uppercase letters should do this already.
next prev parent reply other threads:[~2024-07-24 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 19:58 [BUG] Capital-letter options from dangling clock don't clock out [9.8-pre (release_9.7.7-106-g114c76 @ /home/rens/Projects/org/org-mode/lisp/)] Rens Oliemans
2024-07-24 10:26 ` Ihor Radchenko
2024-07-24 11:31 ` Rens Oliemans [this message]
2024-07-24 11:33 ` Rens Oliemans
2024-07-24 13:46 ` Ihor Radchenko
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=87bk2njaaa.fsf@rensoliemans.nl \
--to=hallo@rensoliemans.nl \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).