From: Kyle Meyer <kyle@kyleam.com>
To: Dmitrii Korobeinikov <dim1212k@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: org-clock misleading description for a prompt option
Date: Fri, 10 Apr 2020 04:47:19 +0000 [thread overview]
Message-ID: <87y2r40wx4.fsf@kyleam.com> (raw)
In-Reply-To: <CA+Yh0STnKPDsTezT_jSxzuvpUgiOm6YUcPYKCfDWTj-Q_zP9Ng@mail.gmail.com>
Dmitrii Korobeinikov <dim1212k@gmail.com> writes:
> When you run org-clock-in and then restart emacs, clocking in again
> will show a prompt asking what to do w/ the unfinished entry. "i"
> means "ignore this question; the same as keeping all the idle time".
> However, a new entry is created if this is chosen without doing
> anything about unfinished one. Keeping all the idle time w/ "k"
> updates the unfinished entry before starting a new one. "i" doesn't do
> that, so the description seems a bit misleading.
That seems confusing to me as well (at least being the not-advanced
clocker that I am). I suspect the confusion comes from the different
perspective from which it's written. You're talking about restarting
Emacs and clocking in again; the description is, I think, written
assuming the context of the prompt being triggered due to idle time. In
that scenario, hitting i/q or 'k => all' have the same effect; a new
entry is not created.
This resolving on clock-in vs resolving when idle discrepancy shows in
at least one other part of the description: the final sentence says that
the uppercase variants leads to a clocked out state, but that's not true
when org-clock-resolve is triggered from an org-clock-in call.
So, while I think things could be improved here (contributions welcome),
those changes should keep both contexts in mind.
next prev parent reply other threads:[~2020-04-10 4:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 10:41 org-clock misleading description for a prompt option Dmitrii Korobeinikov
2020-04-10 4:47 ` Kyle Meyer [this message]
2020-04-10 16:57 ` Dmitrii Korobeinikov
2020-04-10 21:40 ` Kyle Meyer
2020-04-11 10:12 ` Dmitrii Korobeinikov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2r40wx4.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=dim1212k@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.