From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: org-clock-display on org-narrow-to-subtree Date: Tue, 02 Oct 2007 14:33:32 -0400 Message-ID: <87641picxv.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 1Icn4c-0006gj-31 for emacs-orgmode@gnu.org; Tue, 02 Oct 2007 15:06:26 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Icn4a-0006do-1V for emacs-orgmode@gnu.org; Tue, 02 Oct 2007 15:06:25 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Icn4Z-0006dg-Up for emacs-orgmode@gnu.org; Tue, 02 Oct 2007 15:06:23 -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 1Icn4Z-0001L1-G8 for emacs-orgmode@gnu.org; Tue, 02 Oct 2007 15:06:23 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Icn0A-0000uS-Vl for emacs-orgmode@gnu.org; Tue, 02 Oct 2007 19:01:51 +0000 Received: from cpe000102d0fe75-cm0012256ecbde.cpe.net.cable.rogers.com ([74.119.210.211]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 02 Oct 2007 19:01:50 +0000 Received: from bernt by cpe000102d0fe75-cm0012256ecbde.cpe.net.cable.rogers.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 02 Oct 2007 19:01:50 +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 Carsten, I just noticed a minor thing with org-clock-display. I'm using org-narrow-to-subtree regularly now that I've tried again to switch to GTD :) and org-clock-display (C-c C-x C-d) in the narrowed buffer doesn't put the time on the first line (which is the parent task). My current workaround for this is just to insert a blank line at the top of the buffer - then it works. I just have to remember to remove the blank line before widening the buffer again. Hopefully there's a simple fix for this. Thanks again for a (as my 6-year old would call it) TOTALLY AWESOME tool! Regards, Bernt