From mboxrd@z Thu Jan 1 00:00:00 1970 From: John J Foerch Subject: Re: org-log-note-headings 'state Date: Thu, 29 Mar 2012 18:45:56 -0400 Message-ID: <87k423jaaj.fsf@hecubus.retroj.net> References: <873992lmm8.fsf@hecubus.retroj.net> <874nt9of38.fsf@gnu.org> <87vclpjy02.fsf@hecubus.retroj.net> <4F74D3C0.80005@alum.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([208.118.235.92]:50772) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SDO6k-0005k5-N2 for emacs-orgmode@gnu.org; Thu, 29 Mar 2012 18:46:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SDO6j-00025M-0M for emacs-orgmode@gnu.org; Thu, 29 Mar 2012 18:46:18 -0400 Received: from plane.gmane.org ([80.91.229.3]:54363) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SDO6i-00025H-Pg for emacs-orgmode@gnu.org; Thu, 29 Mar 2012 18:46:16 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1SDO6d-0006gu-HW for emacs-orgmode@gnu.org; Fri, 30 Mar 2012 00:46:11 +0200 Received: from 236.sub-75-198-33.myvzw.com ([75.198.33.236]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 30 Mar 2012 00:46:11 +0200 Received: from jjfoerch by 236.sub-75-198-33.myvzw.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 30 Mar 2012 00:46: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 Ilya Shlyakhter writes: > On 3/27/2012 9:49 PM, John J Foerch wrote: >>>> 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. >> I have been experimenting with parsing the format-string to build a >> regexp to match the generated-strings. This approach depends upon the >> parsability of the expansions of each of the percent-codes. As concerns >> org-log-note-headings, %t, %T, %d, %D, %s, %S, and %u all have parseable >> expansions, as far as I can tell. I'm not sure about %U, but if the >> rest of the string is not too complicated, it shouldn't be a problem. >> Format-code flag, width, and precision add some complexity to the >> problem of generating regexps to match the codes, and I haven't done >> that bit yet. Overall I think this could be a very viable approach, and >> I'll paste my scraps of code below: >> >> ;;; parsing state changes >> ;;; > > Thanks a lot -- I also need the ability to parse state changes for an > extension I am writing. It'll be very useful if you could post the > final working version of your patch for this. > > thanks, > > ilya Will do. -- John Foerch