From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Support (or not) for Emacs 21, and XEmacs Date: Fri, 16 Apr 2010 16:42:42 +0200 Message-ID: <01F3859A-1BDB-4F9C-A523-B3235A055F0D@uva.nl> References: <15649C3E-517D-433D-977F-06008C20A4F4@gmail.com> <87k4s7mtvk.fsf@gmx.de> <874ojb4k1t.fsf@gollum.intra.norang.ca> <237EB140-6923-47B2-8991-511BEAA6C682@uva.nl> <87r5mf31do.fsf@gollum.intra.norang.ca> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O2mkt-0003Yt-Ql for emacs-orgmode@gnu.org; Fri, 16 Apr 2010 10:42:51 -0400 Received: from [140.186.70.92] (port=34926 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O2mkr-0003Y4-R5 for emacs-orgmode@gnu.org; Fri, 16 Apr 2010 10:42:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O2mko-0004XS-B5 for emacs-orgmode@gnu.org; Fri, 16 Apr 2010 10:42:49 -0400 Received: from postduif.ic.uva.nl ([145.18.40.180]:35113) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O2mko-0004XL-3U for emacs-orgmode@gnu.org; Fri, 16 Apr 2010 10:42:46 -0400 In-Reply-To: <87r5mf31do.fsf@gollum.intra.norang.ca> 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: Bernt Hansen Cc: Org-Mode List On Apr 16, 2010, at 4:42 PM, Bernt Hansen wrote: > Thanks. I'll beat on it some more :) What a team! :-) > > Regards, > Bernt > > Carsten Dominik writes: > >> Hi Bernt, thanks a lot for this report - I believe I know >> what was causing this and have fixed it, still on that branch of >> course. >> >> - Carsten >> >> On Apr 16, 2010, at 3:13 PM, Bernt Hansen wrote: >> >>> Found a bug. >>> > > > >>> Clocking in doesn't work correctly. >>> >>> I have a task like this >>> >>> ,----[ x.org ] >>> | * TODO foo >>> | :CLOCK: >>> | CLOCK: [2010-04-16 Fri 09:10]--[2010-04-16 Fri 09:11] => 0:01 >>> | :END: >>> | >>> | ** TODO Bar baz >>> | [2010-04-16 Fri 09:10] >>> `---- >>> >>> if the parent task is clocking I can't clock in the subtask - the >>> parent >>> task continues to clock and the point is moved to the headline of >>> the >>> parent task. Same behaviour on both versions. >>> >>> Switching back to master until this is fixed since I can't function >>> without working clocking :) - Carsten