all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John J Foerch <jjfoerch@earthlink.net>
To: emacs-orgmode@gnu.org
Subject: org-log-note-headings 'state
Date: Tue, 20 Mar 2012 22:21:51 -0400	[thread overview]
Message-ID: <873992lmm8.fsf@hecubus.retroj.net> (raw)

Hello,

I'm writing an extension for org-mode wherein it would be incredibly
convenient to be able to parse the state changes inside of LOGBOOK
drawers to get the state-names and timestamps.  However, I find that
state changes are currently only parsable in an ad hoc manner, as for
example by org-agenda-log-mode.  The docsting of org-log-note-headings
mentions this:

  "In fact, it is not a good idea to change the `state' entry, because
  agenda log mode depends on the format of these entries."

It is disappointing to me that the state entry of org-log-note-headings
is not safely user-configurable because of this.  Personally, I do like
to configure it to something a little cleaner and easier to read,
("State -> %s  %d").  (I haven't yet used org-agenda-log-mode, so haven't
run into the problems warned of in the docstring.)  If I were to do ad
hoc parsing of state changes in the mode I'm writing, I would have to
give up my local configuration of the state entry of org-log-note-headings.

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.

Thoughts?

-- 
John Foerch

             reply	other threads:[~2012-03-21  2:22 UTC|newest]

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

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

  git send-email \
    --in-reply-to=873992lmm8.fsf@hecubus.retroj.net \
    --to=jjfoerch@earthlink.net \
    --cc=emacs-orgmode@gnu.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.