Re: [O] Bug: Reading currently clocked headline interferes with org-capture-finalize [8.3.4 (8.3.4-93-g0d72c3-elpaplus @ /home/joe/.emacs.d/elpa/org-20160627/)]

2016-07-31 Thread Joe Schafer
Awesome, it works! Thank you for the quick reply and fix. On Fri, Jul 29, 2016 at 1:03 AM Joe Schafer wrote: > > I have a function to save the currently clocked item into a file so I > can display it in my terminal. The hook seems to interfere with > org-capture. If I

Re: [O] Bug: Reading currently clocked headline interferes with org-capture-finalize [8.3.4 (8.3.4-93-g0d72c3-elpaplus @ /home/joe/.emacs.d/elpa/org-20160627/)]

2016-07-30 Thread Nicolas Goaziou
Hello, Joe Schafer writes: > I have a function to save the currently clocked item into a file so I > can display it in my terminal. The hook seems to interfere with > org-capture. If I capture something the following > happens: > > 1. org-capture dialog appears > 2.

Re: [O] Bug: Reading currently clocked headline interferes with org-capture-finalize [8.3.4 (8.3.4-93-g0d72c3-elpaplus @ /home/joe/.emacs.d/elpa/org-20160627/)]

2016-07-30 Thread Adam Porter
Nicolas Goaziou writes: > FWIW I cannot reproduce it on development version with the following > template: > > ("c" "clocks" entry >(file "/tmp/bug.org") "* %?" :clock-in t :clock-resume t) > > IOW the previous clock is properly resumed. Thanks, Nicolas. I'll have

Re: [O] Bug: Reading currently clocked headline interferes with org-capture-finalize [8.3.4 (8.3.4-93-g0d72c3-elpaplus @ /home/joe/.emacs.d/elpa/org-20160627/)]

2016-07-30 Thread Nicolas Goaziou
Hello, Adam Porter writes: > Joe, thanks for reporting this! I have been noticing this for a while > now, but I always thought it must have been a config problem on my > end. (Or maybe it is, and we both have it? haha) > > Just to be clear, here's how I seem to experience

Re: [O] Bug: Reading currently clocked headline interferes with org-capture-finalize [8.3.4 (8.3.4-93-g0d72c3-elpaplus @ /home/joe/.emacs.d/elpa/org-20160627/)]

2016-07-29 Thread Adam Porter
Joe, thanks for reporting this! I have been noticing this for a while now, but I always thought it must have been a config problem on my end. (Or maybe it is, and we both have it? haha) Just to be clear, here's how I seem to experience it: 1. Clock in any item. 2. Run org-capture with a