emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Christopher W. Ryan" <cryan@binghamton.edu>
To: Michael Welle <mwe012008@gmx.net>, emacs-orgmode@gnu.org
Subject: Re: how do I search state change dates?
Date: Sat, 12 Jan 2019 18:43:40 -0500	[thread overview]
Message-ID: <b6dc7822-4823-fa78-8f6d-ae04a867b0c4@binghamton.edu> (raw)
In-Reply-To: <87bm4yamni.fsf@luisa.c0t0d0s0.de>

This looks promising. However, the example at the link you referenced
seems to have its state changes inside a LOGBOOK property drawer. My
state changes are not inside a drawer. See excerpt below.  To change the
state, say from TODO to READING, I use C-c C-t and then can choose one
of my pre-specified states.  Should I put my state changes in a LOGBOOK
drawer? If so, how does that work?

** DONE Responsible Men		 :fiction:BUlibrary:
   - State "DONE"       from "READING"    [2018-11-18 Sun 23:17]
   - State "READING"    from "TODO"       [2018-11-04 Sun 23:17]
   :PROPERTIES:
   :AUTHORLNAME: Schwarzschild
   :AUTHORFNAME: Edward
   :ISBN: 156512409X
   :END:

Thanks.

--Chris Ryan

Michael Welle wrote:
> Hello,
> 
> "Christopher W. Ryan" <cryan@binghamton.edu> writes:
> 
>> I try to keep track of books I want to read, and when I eventually read
>> them.  I use TODO keyword for books I intend to read, and I change the
>> state to READING and then DONE, as appropriate. Each state change gets a
>> date/time stamp.
> at [0] you will find a bit of code (org-task-dump-logs.el) that
> retrieves all the log data for a given task. Maybe that is helpful if
> you extend it with a loop that iterates over all tasks of a file.
> 
> Regards
> hmw
> 
> [0] https://www.c0t0d0s0.de/otdl/otdl.html
> 

  reply	other threads:[~2019-01-12 23:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-01 19:16 how do I search state change dates? Christopher W. Ryan
2019-01-02 14:59 ` Eric S Fraga
2019-01-02 19:24 ` Michael Welle
2019-01-12 23:43   ` Christopher W. Ryan [this message]
2019-01-13  6:02     ` Michael Welle

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=b6dc7822-4823-fa78-8f6d-ae04a867b0c4@binghamton.edu \
    --to=cryan@binghamton.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=mwe012008@gmx.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).