emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Juan Pechiar <juan@pechiar.com>
To: John J Foerch <jjfoerch@earthlink.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: feature request for org-store-log-note
Date: Tue, 27 Sep 2011 23:28:06 -0300	[thread overview]
Message-ID: <20110928022806.GA15758@soloJazz.com> (raw)
In-Reply-To: <8762kdcwvk.fsf@hecubus.retroj.net>

Hi John,

Please check the variable

   org-log-states-order-reversed

Documentation:
Non-nil means the latest state note will be directly after heading.
When nil, the state change notes will be ordered according to time.

Regards,
.j.

On Tue, Sep 27, 2011 at 08:51:27PM -0400, John J Foerch wrote:
> I use org to manage TODO lists in which I want to keep time stamps for
> the creation of an item, and for each state change.  To be as clear as
> possible, I'll just paste the portion of my config that affects how
> TODOs work:
>
>   (setq org-treat-insert-todo-heading-as-state-change t
>         org-log-into-drawer t
>         org-log-done nil)
>
>   (setq org-todo-keywords
>         '((sequence "TODO(t!)" "|" "DONE(d!)" "CANCELLED(c!)")))
>
>   (setcdr (assq 'state org-log-note-headings)
>           "State -> %s  %t")
>
> This logs each state change (including creation) into the LOGBOOK
> drawer.  It's great.  My feature request concerns the order in which the
> notes are logged.  Each new note is inserted at the top of the drawer.
> I would prefer it if they could be logged to the end of the drawer, so
> that one could read all of the state changes in chronological order from
> the top down.

  reply	other threads:[~2011-09-28  2:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-28  0:51 feature request for org-store-log-note John J Foerch
2011-09-28  2:28 ` Juan Pechiar [this message]
2011-09-28  3:45   ` John J Foerch
2011-10-05  0:15 ` Storing log notes at capture (was Re: feature request for org-store-log-note) Olaf Meeuwissen

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=20110928022806.GA15758@soloJazz.com \
    --to=juan@pechiar.com \
    --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
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 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).