From mboxrd@z Thu Jan 1 00:00:00 1970 From: Manish Subject: Re: Clocktable: Include non-clock items Date: Thu, 4 Mar 2010 08:19:06 +0530 Message-ID: References: <211769421003031221q634f0a19ud458ef43a6fcd38a@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Nn180-0006RQ-68 for emacs-orgmode@gnu.org; Wed, 03 Mar 2010 21:49:32 -0500 Received: from [140.186.70.92] (port=50607 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nn17y-0006RI-Au for emacs-orgmode@gnu.org; Wed, 03 Mar 2010 21:49:30 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Nn17x-0007Zw-HC for emacs-orgmode@gnu.org; Wed, 03 Mar 2010 21:49:30 -0500 Received: from mail-iw0-f185.google.com ([209.85.223.185]:56544) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Nn17x-0007ZO-EA for emacs-orgmode@gnu.org; Wed, 03 Mar 2010 21:49:29 -0500 Received: by iwn15 with SMTP id 15so1718427iwn.7 for ; Wed, 03 Mar 2010 18:49:27 -0800 (PST) In-Reply-To: <211769421003031221q634f0a19ud458ef43a6fcd38a@mail.gmail.com> 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: Nathan Neff Cc: emacs-orgmode@gnu.org On Thu, Mar 4, 2010 at 1:51 AM, Nathan Neff wrote: > Is there a way to get a clock table to show items > that do not have a clock entry? i don't think so. > > > Here's the use-case: > > I'm working on Task 1, and encounter an unusual problem. > I want my clock report to show some detail about why Task 1 > took more time than usual. > > I don't want to create a sub-heading and clock into it, and > adjust the clock, etc. I just want to store a note about this, and > have the note appear in the clock report. i understand that creating a new task and adjusting clocks could be more context switches than you'd like but once you have setup and executed a few times following may not really a big diversion although it does require one to be conscious of the change in the nature of task as it happens (e.g. unusual problem delaying the task.) 1. call remember to create a child task (so the child's clock time contributes towards the parent task) 2. remember clocks in to the task automatically and can record a link to the task was interrupted by creation of this one (%K in a remember template) 3. once this task is over you clock back into the interrupted task #3 probably sounds like something you don't want to do. Bernt Hanson has documented his setup in abundant detail and that has helped me a lot. i'd specifically point you to his " SPC" setup. references: 1. http://doc.norang.ca/org-mode.html#Remember 2. http://doc.norang.ca/org-mode.html#Clocking hth, -- manish