emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Ilya Shlyakhter <ilya_shl@alum.mit.edu>
To: John J Foerch <jjfoerch@earthlink.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-log-note-headings 'state
Date: Thu, 29 Mar 2012 17:27:28 -0400	[thread overview]
Message-ID: <4F74D3C0.80005@alum.mit.edu> (raw)
In-Reply-To: <87vclpjy02.fsf@hecubus.retroj.net>

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

next prev parent reply	other threads:[~2012-03-29 21:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-21  2:21 org-log-note-headings 'state John J Foerch
2012-03-27 22:26 ` Bastien
2012-03-28  1:49   ` John J Foerch
2012-03-29 21:27     ` Ilya Shlyakhter [this message]
2012-03-29 22:45       ` John J Foerch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F74D3C0.80005@alum.mit.edu \
    --to=ilya_shl@alum.mit.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=jjfoerch@earthlink.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).