From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: org-agenda-log-mode change Date: Mon, 15 Oct 2007 11:13:42 -0400 Message-ID: <878x648l7d.fsf@gollum.intra.norang.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IhSbr-0008Av-Dq for emacs-orgmode@gnu.org; Mon, 15 Oct 2007 12:16:03 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IhSbk-00088k-Nr for emacs-orgmode@gnu.org; Mon, 15 Oct 2007 12:16:02 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IhSbk-00088d-Cp for emacs-orgmode@gnu.org; Mon, 15 Oct 2007 12:15:56 -0400 Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1IhSbj-0004Wy-A3 for emacs-orgmode@gnu.org; Mon, 15 Oct 2007 12:15:56 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IhS2E-0002gR-B3 for emacs-orgmode@gnu.org; Mon, 15 Oct 2007 15:39:14 +0000 Received: from cpe000102d0fe75-cm0012256ecbde.cpe.net.cable.rogers.com ([99.239.148.180]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 15 Oct 2007 15:39:14 +0000 Received: from bernt by cpe000102d0fe75-cm0012256ecbde.cpe.net.cable.rogers.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 15 Oct 2007 15:39:14 +0000 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 Carsten, I just noticed today that org-agenda-log-mode isn't sorting the same was as it used to. Displayed clocked items used to be in ascending time order but now they seem to be all mixed up (or sorted by category first) and they have no time display in the agenda anymore. Without org-clock-goto this would have been much more of a problem for me. Was this change intentional or an oversight? I'm using Org-mode version 5.12c (as of a few minutes ago but it's the same in 5.12a.) Here is my agenda from today (with the task names and categories renamed) to show the difference in the display I'm seeing. ,----[ 5.11b.txt ] | Day-agenda: | Monday 15 October 2007 | CCCC: 7:41...... Closed: DONE Some Task 1 | Org: 7:41...... Clocked: TODO Some Task 2 | nnnnnn: 7:43...... Clocked: TODO Some Task 3 | sssss: 7:46...... Clocked: TODO Some Task 4 | Misc: 8:18...... Clocked: TODO Some Task 5 | sssss: 8:21...... Clocked: NEXT Some Task 6 | CCCC: 8:25...... Clocked: ONGOING Some Task 7 | HHH: 10:38...... Closed: DONE Some Task 8 | HHH: 10:38...... Closed: DONE Some Task 9 | HHH: 10:43...... Clocked: NEXT Some Task 10 | CCC*: Sched. 5x: TODO Some Task 11 | HHH: Sched. 5x: TODO Some Task 12 | HHH: Sched. 5x: NEXT Some Task 13 | 8:00...... ---------------- | 10:00...... ---------------- | 12:00...... ---------------- | 14:00...... ---------------- | 16:00...... ---------------- | 18:00...... ---------------- | 20:00...... ---------------- `---- ,----[ 5.12c ] | Day-agenda: | Monday 15 October 2007 | CCCC: Clocked: ONGOING Some Task 7 | CCCC: Closed: DONE Some Task 1 | HHH: Clocked: NEXT Some Task 10 | HHH: Closed: DONE Some Task 8 | HHH: Closed: DONE Some Task 9 | Misc: Clocked: TODO Some Task 5 | Org: Clocked: TODO Some Task 2 | nnnnnn: Clocked: TODO Some Task 3 | sssss: Clocked: NEXT Some Task 6 | sssss: Clocked: TODO Some Task 4 | CCC*: Sched. 5x: TODO Some Task 11 | HHH: Sched. 5x: TODO Some Task 12 | HHH: Sched. 5x: NEXT Some Task 13 `---- Regards, Bernt