[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] Subject: Bug: org-time-stamp-inactive on the end of a CLOCK inte
From: |
Christoph LANGE |
Subject: |
Re: [O] Subject: Bug: org-time-stamp-inactive on the end of a CLOCK interval edits start time [8.3.1 (8.3.1-elpaplus @ c:/Users/clange/.emacs.d/elpa/org-plus-contrib-20150805/)] |
Date: |
Mon, 10 Aug 2015 13:28:16 +0200 |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 |
Hi Nicolas,
Nicolas Goaziou on 2015-08-10 09:29:
> You can bisect your configuration to find out the wrong part. You can
> also check what is called by C-c ! with your configuration.
C-c ! and C-c . call org-time-stamp[-inactive] in my full configuration.
And now I'm sure that I'm _always_ getting the wrong behaviour I
reported initially.
When I said in my previous email that I didn't get the wrong behaviour
with "emacs -q" this was wrong, because "emacs -q" doesn't load org-mode
8.3.1, which I installed from elpa, but loads the bundled org-mode 8.2.x.
Running "emacs -q" and then (package-initialize) and then opening a
minimal file like
* Hello
CLOCK: [2015-08-07 Fri 10:14]--[2015-08-07 Fri 10:20] => 0:06
was enough to reproduce the bug. I.e. C-c ! or C-c . on the second
timestamp prompted me with the time of the first one.
Cheers,
Christoph
--
Dr. Christoph Lange, Enterprise Information Systems Department
Applied Computer Science @ University of Bonn; Fraunhofer IAIS
http://langec.wordpress.com/about, Skype duke4701
→ Web Intelligence Summer School “Question Answering with the Web”
Saint-Étienne, FR. Apply by 4 July @ https://wiss.univ-st-etienne.fr/