From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: special status for state-log plain list elements?
Date: Tue, 10 Jun 2014 21:58:29 +0200
Message-ID: <8761k8ilju.fsf@selenimh.mobile.lan>
References: <87k38p4fyu.fsf@ericabrahamsen.net>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:35372)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1WuSBr-0000Te-MZ
	for emacs-orgmode@gnu.org; Tue, 10 Jun 2014 15:58:47 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1WuSBh-0005PA-Jv
	for emacs-orgmode@gnu.org; Tue, 10 Jun 2014 15:58:39 -0400
Received: from relay5-d.mail.gandi.net ([2001:4b98:c:538::197]:56334)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1WuSBh-0005N0-DP
	for emacs-orgmode@gnu.org; Tue, 10 Jun 2014 15:58:29 -0400
In-Reply-To: <87k38p4fyu.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of
	"Tue, 10 Jun 2014 11:10:33 +0800")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-orgmode@gnu.org

Hello,

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> 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.

I don't think what is done with lists has much to do with their syntax.
Anyway, you can write a function to find such candidates, if needed,
without overloading the parser (for little benefit).

> 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).

This is not really possible, unless you forbid users to arbitrary start
an item with "State "xxx" from "xxx"" or "Note taken on", i.e., you
bless them as parts of Org syntax. I wouldn't go that far.


Regards,

-- 
Nicolas Goaziou