From mboxrd@z Thu Jan 1 00:00:00 1970 From: John J Foerch Subject: org-log-note-headings 'state Date: Tue, 20 Mar 2012 22:21:51 -0400 Message-ID: <873992lmm8.fsf@hecubus.retroj.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([208.118.235.92]:36448) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SABBe-000330-M5 for emacs-orgmode@gnu.org; Tue, 20 Mar 2012 22:22:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SABBd-0008Nr-1Z for emacs-orgmode@gnu.org; Tue, 20 Mar 2012 22:22:06 -0400 Received: from plane.gmane.org ([80.91.229.3]:42355) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SABBc-0008Ni-RK for emacs-orgmode@gnu.org; Tue, 20 Mar 2012 22:22:04 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1SABBa-0005fu-R9 for emacs-orgmode@gnu.org; Wed, 21 Mar 2012 03:22:02 +0100 Received: from 49.sub-75-241-97.myvzw.com ([75.241.97.49]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 21 Mar 2012 03:22:02 +0100 Received: from jjfoerch by 49.sub-75-241-97.myvzw.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 21 Mar 2012 03:22:02 +0100 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@gnu.org Hello, I'm writing an extension for org-mode wherein it would be incredibly convenient to be able to parse the state changes inside of LOGBOOK drawers to get the state-names and timestamps. However, I find that state changes are currently only parsable in an ad hoc manner, as for example by org-agenda-log-mode. The docsting of org-log-note-headings mentions this: "In fact, it is not a good idea to change the `state' entry, because agenda log mode depends on the format of these entries." It is disappointing to me that the state entry of org-log-note-headings is not safely user-configurable because of this. Personally, I do like to configure it to something a little cleaner and easier to read, ("State -> %s %d"). (I haven't yet used org-agenda-log-mode, so haven't run into the problems warned of in the docstring.) If I were to do ad hoc parsing of state changes in the mode I'm writing, I would have to give up my local configuration of the state entry of org-log-note-headings. These thoughts lead me to suggest that maybe org-log-note-headings is no longer sufficient to its original purpose, because extensions wish to parse state changes, but that blocks users from configuring the formats. Perhaps it is time to replace it with something that guarantees ability to parse. Thoughts? -- John Foerch