From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Journal versus clock tables: Opposing requirements? Date: Tue, 8 Nov 2011 09:23:19 +0100 Message-ID: <68F95387-0EDF-4848-BFD1-E7DF045BABDA@gmail.com> References: <87hb2ggoju.fsf@norang.ca> <87wrbbfgf4.fsf@norang.ca> Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([140.186.70.92]:44080) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RNgxo-0003gj-FC for emacs-orgmode@gnu.org; Tue, 08 Nov 2011 03:23:26 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RNgxn-00027m-J7 for emacs-orgmode@gnu.org; Tue, 08 Nov 2011 03:23:24 -0500 Received: from mail-ey0-f169.google.com ([209.85.215.169]:46527) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RNgxn-00027X-EU for emacs-orgmode@gnu.org; Tue, 08 Nov 2011 03:23:23 -0500 Received: by eye4 with SMTP id 4so137139eye.0 for ; Tue, 08 Nov 2011 00:23:22 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Tommy Kelly Cc: Bernt Hansen , emacs-orgmode@gnu.org On Nov 8, 2011, at 9:06 AM, Tommy Kelly wrote: >> ... it depends on how often you require this weekly report... > > Ermm, weekly :-) > >> It should be possible to write code that walks your agenda, visits the >> tasks, and copies and pastes the details to a temporary org buffer/file >> just for your chronological report. > > Absolutely. But as I've been thinking about this, I'm realizing that > in fact a key input requirement (as opposed to my two output > requirements -- chronology plus clock tables) is ease of entry. As I > begin some new chunk of work, I don't want to have to hunt around for > the most appropriate heading to clock into and begin writing notes > under. As a result, what's happening is two things. First, I'm just > falling back on your single "Organization" catch-all task; second, I'm > not writing *any* notes. > > With a chronological journal, there's no decision to be made. You just > start logging at the end (or start) of the journal. But maybe > something in the org-capture area is what I need. I've tried it before > and didn't get very far, but I'll have another look. Yes, capture you notes into a date tree and turn on the clock whenever you start a new entry! - Carsten