Subject: Bug: Org-Clock-Out in indirect buffer error after refile [9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)]

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]

[-- Attachment #1: Type: text/plain, Size: 581 bytes --]

Emacs  : GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.24.23, cairo version 1.16.0)
 of 2021-01-18, modified by Debian
Package: Org mode version 9.3 (release_9.3 @
/usr/share/emacs/27.1/lisp/org/)

Hi,

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".

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.

Thanks in advance.

Regards,

- Eddie Drury

[-- Attachment #2: Type: text/html, Size: 775 bytes --]

Re: Subject: Bug: Org-Clock-Out in indirect buffer error after refile [9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)]

[Bhavin Gandhi]

Hello Eddie

On Mon, 19 Jul 2021 at 16:15, Eddie Drury <eddie.drury@gmail.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

#+begin_src org
* Read Org mode list
** Triage bugs

* Read Emacs bugs list

#+end_src

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.

-- 
Regards,
Bhavin Gandhi (bhavin192) | https://geeksocket.in

Re: 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]

[-- Attachment #1: Type: text/plain, Size: 1671 bytes --]

Hi Bhavin,

Thanks for your prompt response.

I have followed those steps and that is the same behaviour I get.

The expected behaviour is for it to clock out of the subtree, instead of
giving the "Clock start time is gone" error.

Regards,

- Eddie Drury

On Wed, 21 Jul 2021 at 02:00, Bhavin Gandhi <bhavin7392@gmail.com> wrote:

> Hello Eddie
>
> On Mon, 19 Jul 2021 at 16:15, Eddie Drury <eddie.drury@gmail.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
>
> #+begin_src org
> * Read Org mode list
> ** Triage bugs
>
> * Read Emacs bugs list
>
> #+end_src
>
> 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.
>
> --
> Regards,
> Bhavin Gandhi (bhavin192) | https://geeksocket.in
>

[-- Attachment #2: Type: text/html, Size: 2538 bytes --]

[PATCH] Re: Subject: Bug: Org-Clock-Out in indirect buffer error after refile [9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)]

[Ihor Radchenko]

[-- Attachment #1: Type: text/plain, Size: 294 bytes --]

Eddie Drury <eddie.drury@gmail.com> writes:

> I have followed those steps and that is the same behaviour I get.
>
> The expected behaviour is for it to clock out of the subtree, instead of
> giving the "Clock start time is gone" error.

I can also reproduce. The fix is attached.

Best,
Ihor


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Fix-not-updating-org-clock-marker-after-refiling-fro.patch --]
[-- Type: text/x-diff, Size: 1290 bytes --]

From 4ad92b3efc8717e3ca871ab83bcb5e23e8faeb35 Mon Sep 17 00:00:00 2001
Message-Id: <4ad92b3efc8717e3ca871ab83bcb5e23e8faeb35.1627654962.git.yantar92@gmail.com>
From: Ihor Radchenko <yantar92@gmail.com>
Date: Fri, 30 Jul 2021 22:16:02 +0800
Subject: [PATCH] Fix not updating org-clock-marker after refiling from
 indirect buffer

* lisp/org.el (org-check-and-save-marker): Save markers in base buffer
of indirect buffer in addition to markers in current buffer.

Fixes bug reported in https://orgmode.org/list/CABa5=g4bvYQoTbBn96tFi9K827u_A+MweqYWWpib_tyFLBdG3g@mail.gmail.com/T/#t
---
 lisp/org.el | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/lisp/org.el b/lisp/org.el
index eca12a5e7..53fd5b7c7 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -7877,7 +7877,8 @@ (defun org-check-and-save-marker (marker beg end)
   "Check if MARKER is between BEG and END.
 If yes, remember the marker and the distance to BEG."
   (when (and (marker-buffer marker)
-	     (equal (marker-buffer marker) (current-buffer))
+	     (or (equal (marker-buffer marker) (current-buffer))
+                 (equal (marker-buffer marker) (buffer-base-buffer (current-buffer))))
 	     (>= marker beg) (< marker end))
     (push (cons marker (- marker beg)) org-markers-to-move)))
 
-- 
2.31.1

Re: [PATCH] Re: Subject: Bug: Org-Clock-Out in indirect buffer error after refile [9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)]

[Bastien]

Hi Ihor,

Ihor Radchenko <yantar92@gmail.com> writes:

> Eddie Drury <eddie.drury@gmail.com> writes:
>
>> I have followed those steps and that is the same behaviour I get.
>>
>> The expected behaviour is for it to clock out of the subtree, instead of
>> giving the "Clock start time is gone" error.
>
> I can also reproduce. The fix is attached.

Applied, thanks!