Re: [O] Bug: org-resolve-clocks should not iterate over non-agenda org files [8.3.3 (8.3.3-elpaplus @ /home/dfeich/.emacs.d/elpa/org-plus-contrib-20160108/)

Hello, Derek Feichtinger writes: > The thing which made it hard for me to identify the initial problem was > that the test CLOCK lines I had in the testing file where placed there > without a heading. When later in the day I wanted to clock in to my tasks, > I then just ended

Re: [O] Bug: org-resolve-clocks should not iterate over non-agenda org files [8.3.3 (8.3.3-elpaplus @ /home/dfeich/.emacs.d/elpa/org-plus-contrib-20160108/)

Hi Nicolas Ok, that makes sense, then. Probably there are other users who indeed will rely on clocking in non-agenda files. The thing which made it hard for me to identify the initial problem was that the test CLOCK lines I had in the testing file where placed there without a heading. When later

Re: [O] Bug: org-resolve-clocks should not iterate over non-agenda org files [8.3.3 (8.3.3-elpaplus @ /home/dfeich/.emacs.d/elpa/org-plus-contrib-20160108/)

Hello, Derek Feichtinger writes: > org-resolve-clock loops over all open org buffers for detecting open > clocks (using function org-files-list). Is this really intended? I think > it should just loop over the org-agenda-files. > > I was working on an extension for clocking

[O] Bug: org-resolve-clocks should not iterate over non-agenda org files [8.3.3 (8.3.3-elpaplus @ /home/dfeich/.emacs.d/elpa/org-plus-contrib-20160108/)

Hi org-resolve-clock loops over all open org buffers for detecting open clocks (using function org-files-list). Is this really intended? I think it should just loop over the org-agenda-files. I was working on an extension for clocking and was recording my testing results into a separate org