From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Abrahamsen Subject: Re: special status for state-log plain list elements? Date: Wed, 11 Jun 2014 09:54:12 +0800 Message-ID: <87egywcit7.fsf@ericabrahamsen.net> References: <87k38p4fyu.fsf@ericabrahamsen.net> <8761k8ilju.fsf@selenimh.mobile.lan> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33966) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WuXgj-0003sS-OK for emacs-orgmode@gnu.org; Tue, 10 Jun 2014 21:50:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WuXge-0002Lq-C0 for emacs-orgmode@gnu.org; Tue, 10 Jun 2014 21:50:53 -0400 Received: from plane.gmane.org ([80.91.229.3]:52558) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WuXge-0002Li-5E for emacs-orgmode@gnu.org; Tue, 10 Jun 2014 21:50:48 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WuXgd-0000Nz-0U for emacs-orgmode@gnu.org; Wed, 11 Jun 2014 03:50:47 +0200 Received: from 222.128.166.14 ([222.128.166.14]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 11 Jun 2014 03:50:47 +0200 Received: from eric by 222.128.166.14 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 11 Jun 2014 03:50:47 +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 Nicolas Goaziou writes: > Hello, > > Eric Abrahamsen 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. Okay, I guess that was the main question I was asking. No worries, then! Thanks, E