From: Bhavin Gandhi <email@example.com>
To: Eddie Drury <firstname.lastname@example.org>
Subject: Re: Subject: Bug: Org-Clock-Out in indirect buffer error after refile [9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)]
Date: Tue, 20 Jul 2021 23:29:38 +0530 [thread overview]
Message-ID: <CAOn=hbdJu9F1ktQv8krD9EoDX5za4XENsnijuv6winiV6bSHew@mail.gmail.com> (raw)
On Mon, 19 Jul 2021 at 16:15, Eddie Drury <email@example.com> wrote:
> When I am working in an indirect buffer and am currently clocked into a subheading. If I refile this subheading and then run org-clock-out, I get the error "Clock start time is gone".
I'm not sure if this is intended behaviour or a bug, but I was able to
reproduce this with the following steps on the latest master. Can you
confirm if you are doing something similar as well?
Content of test.org
* Read Org mode list
** Triage bugs
* Read Emacs bugs list
1. Now go to the "Read Org mode list" entry and run,
org-tree-to-indirect-buffer (C-c C-x b).
2. Switch to the indirect buffer.
3. Go to the "Triage bugs" entry, and run org-clock-in (C-c C-x C-i).
4. Refile the "Triage bugs" entry to "Read Emacs bugs list" with
org-refile (C-c C-w)
5. Switch to test.org buffer, and go to the "Triage bugs" entry, and run
org-clock-out (C-c C-x C-o)
6. This will show "Clock start time is gone"
> When not working in an indirect buffer, Org Mode is able to track this subtree and clock out of it, which is the expected behaviour.
Yes, I found that it is able to track the refile.
Bhavin Gandhi (bhavin192) | https://geeksocket.in
next prev parent reply other threads:[~2021-07-20 18:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 10:43 Subject: Bug: Org-Clock-Out in indirect buffer error after refile [9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)] Eddie Drury
2021-07-20 17:59 ` Bhavin Gandhi [this message]
2021-07-22 10:25 ` Eddie Drury
2021-07-30 14:23 ` [PATCH] " Ihor Radchenko
2021-09-25 21:10 ` Bastien
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).