From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Abrahamsen Subject: special status for state-log plain list elements? Date: Tue, 10 Jun 2014 11:10:33 +0800 Message-ID: <87k38p4fyu.fsf@ericabrahamsen.net> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41492) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WuCPB-0000E5-Jz for emacs-orgmode@gnu.org; Mon, 09 Jun 2014 23:07:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WuCP4-0004YP-1t for emacs-orgmode@gnu.org; Mon, 09 Jun 2014 23:07:21 -0400 Received: from plane.gmane.org ([80.91.229.3]:45954) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WuCP3-0004YJ-RJ for emacs-orgmode@gnu.org; Mon, 09 Jun 2014 23:07:13 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WuCP1-0007Zx-Tx for emacs-orgmode@gnu.org; Tue, 10 Jun 2014 05:07:11 +0200 Received: from 114.248.0.25 ([114.248.0.25]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 10 Jun 2014 05:07:11 +0200 Received: from eric by 114.248.0.25 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 10 Jun 2014 05:07:11 +0200 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 Is there any chance of building slightly on org-element's parsing of plain-lists, so that it lists which represent state logs are somehow noted as such? I'm imagining that `org-element-plain-list-parser' could be augmented to provide a (:log t) property, or if we accept that state-log lists are always unordered, the :type property could even just be 'log. For that it might be nice if list items knew if they were state-change notes (State "WAIT" from "TODO", etc) or plain notes (Note taken on... etc). It's probably feature creep! But it would make some interesting things easier. My most immediate use-case would be a function in the Agenda which shows the most recent state log of the item under point. That way you could see what an item was WAITing on, or what you're actually supposed to do NEXT, and so on. And, in the back of my head, I've always felt that Org should be able to do arbitrary value logging -- sort of a generalization of org-clock. That would be a project for a very rainy day indeed, but this would be a bit of the groundwork done. Anyway, let me know if this would be acceptable in principle (and to what extent), and I can take a stab at a patch. Eric