From: Pete Ley <peteley11235@gmail.com>
To: Daya Atapattu <atapattud@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org-mode Habit with Varying Description
Date: Mon, 20 Oct 2014 10:37:25 -0700 [thread overview]
Message-ID: <87ppdmfxre.fsf@enterprise.sectorq.net> (raw)
In-Reply-To: <CAMaREXYajGgfuX69Z44+NzLW7tBi6PAMdRHTjobqBcndR8My=Q@mail.gmail.com> (Daya Atapattu's message of "Mon, 20 Oct 2014 10:33:19 -0400")
As Bastien said, this doesn't really fit the idea of a habit, but I
think there is a reasonable non-elisp way of tweaking it to fit. Maybe
it would help.
What if you had something like this:
* Read <book>
:LOGBOOK:
- Note taken on [2014-10-20 Mon 10:33] \\
151-300
- Note taken on [2014-10-20 Mon 10:32] \\
1-150
:END:
:PROPERTIES:
:STYLE: habit
:END:
I do this sometimes for things like this. The heading doesn't need to
change as it can just be a reminder to read <book> and you can keep
track of what you've read in the notes with C-c C-z.
Optionally, if you have multiple books and you're reading different
amounts of each one each day, you can just write how much you plan to
read under the heading for each one, e.g.
* Read <book>
100 pages each day
* Read <book 2>
50 pages each day
next prev parent reply other threads:[~2014-10-20 17:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 14:33 Org-mode Habit with Varying Description Daya Atapattu
2014-10-20 14:52 ` Bastien
2014-10-20 15:46 ` Daya Atapattu
2014-10-20 16:02 ` Jorge A. Alfaro-Murillo
2014-10-20 17:37 ` Pete Ley [this message]
2014-10-21 0:34 ` Eric Abrahamsen
2014-10-21 12:21 ` Samuel Loury
2014-10-21 16:29 ` Eric Abrahamsen
2014-10-24 3:42 ` Pete Ley
2014-10-26 15:51 ` Eric Abrahamsen
2014-10-28 13:28 ` Nicolas Goaziou
2014-10-28 13:41 ` Eric Abrahamsen
2014-10-28 15:01 ` Eric Abrahamsen
2014-10-28 16:22 ` Nicolas Goaziou
2014-10-28 16:38 ` Eric Abrahamsen
2014-10-29 20:48 ` Nicolas Goaziou
2014-10-20 19:13 ` Melleus
2014-10-20 20:03 ` Brady Trainor
2014-10-21 15:37 ` Michael Brand
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=87ppdmfxre.fsf@enterprise.sectorq.net \
--to=peteley11235@gmail.com \
--cc=atapattud@gmail.com \
--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.