From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Ring Subject: BUG: clock table gets corrupted (Emacs 21) Date: Mon, 12 Jan 2009 23:42:04 +0100 Message-ID: <496BC73C.6080507@student.tuwien.ac.at> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LMVU5-000566-3B for emacs-orgmode@gnu.org; Mon, 12 Jan 2009 17:42:14 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LMVU1-00055b-Bl for emacs-orgmode@gnu.org; Mon, 12 Jan 2009 17:42:10 -0500 Received: from [199.232.76.173] (port=37312 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LMVU0-00055J-KE for emacs-orgmode@gnu.org; Mon, 12 Jan 2009 17:42:08 -0500 Received: from mail1.student.tuwien.ac.at ([193.170.74.21]:34196) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LMVU0-0002Gk-5I for emacs-orgmode@gnu.org; Mon, 12 Jan 2009 17:42:08 -0500 Received: from macbook-3.chello.at (chello080108206119.5.13.vie.surfer.at [80.108.206.119]) (authenticated bits=0) by mail1.student.tuwien.ac.at (8.13.8/8.13.8) with ESMTP id n0CMfrTu030969 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 12 Jan 2009 23:41:53 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Hi, today I decided to bisect a major annoyance that has bugged me for quite some time now. I'm using a relatively old version of Emacs on Fedora 5. Emacs 21.4.1 from emacs-21.4-14.x86_64.rpm, to be exact. Upon clocking in, a single CLOCK: line is converted to a :CLOCK: block, and this is where the trouble is. On my machine, this is what happens. Before: * Test CLOCK: [2009-01-12 Mon 22:57]--[2009-01-12 Mon 22:57] => 0:00 After clocking in: * Test :CLOCK: CLOCK: [2009-01-12 Mon 22:57]--[2009-01-12 Mon 22:57] => 0:00 :END:CLOCK: [2009-01-12 Mon 23:27] The exact changeset that broke this is: f70127dd3f95473ac80aa407bafca8f68f08e002 And within that specifically the "(org-clock-in): Use org-indent-line-function to indent clock lines." part (+1/-1 line). When I revert this single line in the current head, it starts working again. HTH Stefan