From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael C Gilbert Subject: Re: date added into logbook? Date: Tue, 29 May 2012 10:50:08 -0700 Message-ID: <52CF9819-0135-404F-8F36-FF5CBE0731D3@gilbert.org> References: <27237E64-67BA-4FA4-8365-3EBF9DD00B94@gilbert.org> <6E21786D-C512-4392-A624-DC37E0800A76@gilbert.org> Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:36533) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SZQYf-00039L-N1 for emacs-orgmode@gnu.org; Tue, 29 May 2012 13:50:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SZQYd-0002Pt-Vi for emacs-orgmode@gnu.org; Tue, 29 May 2012 13:50:13 -0400 Received: from peach.gilbert.org ([74.94.69.218]:51745) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SZQYd-0002PT-Mt for emacs-orgmode@gnu.org; Tue, 29 May 2012 13:50:11 -0400 Received: from localhost (localhost [127.0.0.1]) by peach.gilbert.org (Postfix) with ESMTP id C47BDB9C855 for ; Tue, 29 May 2012 10:50:09 -0700 (PDT) Received: from peach.gilbert.org ([127.0.0.1]) by localhost (peach.gilbert.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OHyNv04g330G for ; Tue, 29 May 2012 10:50:09 -0700 (PDT) Received: from [10.1.10.15] (unknown [10.1.10.15]) by peach.gilbert.org (Postfix) with ESMTPSA id 8F912B9C847 for ; Tue, 29 May 2012 10:50:09 -0700 (PDT) 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: emacs-orgmode Mailinglist On May 29, 2012, at 6:04 AM, Jonathan Leech-Pepin wrote: > I'm not sure that you can automatically include the note into a > :LOGBOOK: drawer, however if you're mostly/only working from capture > templates you could add a property for CREATED and have it > automatically fill with an inactive timestamp. Thank you. That's another useful approach.=20 I had this hunch that, in the interest of synergy and re-usability, it = would make sense to tap into the existing framework for managing the = logbook. But from perusing the code, it seems that much of that is kind = baked-in. I'm wondering if someone more familiar with the code base in = question might comment. Am I mistaken? Is there a way to tap into the logbook related loops? =97 Michael