From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: Org-mode Habit with Varying Description
Date: Tue, 21 Oct 2014 08:34:09 +0800 [thread overview]
Message-ID: <87zjcqz2f2.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 87ppdmfxre.fsf@enterprise.sectorq.net
Pete Ley <peteley11235@gmail.com> writes:
> 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've been (very gradually) working on something I'm calling org-log, for
just this sort of situation -- a library that would possibly go
underneath org-habit and maybe even org-clock. It would look like:
* Read <book>
:LOGBOOK:
- Note taken on [2014-10-20 Mon 10:33] \\
PAGES: 49
- Note taken on [2014-10-20 Mon 10:32] \\
PAGES: 150
:END:
When adding notes (or state-change log notes) the user would be prompted
to record values for the key(s) already existing in the logbook (in this
case, PAGES). Multiple key-value pairs would be possible. Generic tables
could be created for a heading, with more specialized tables with
user-defined column formulas and all that.
Add unit manipulation/calculation from the calc-units package, and I
think this could be a nice extension to Org.
I originally started thinking of this while translating a novel. I had a
certain number of characters to translate, and a certain deadline. What
I wanted was a single heading where I logged my progress, and a
reporting facility that said "given today's date and how many characters
you've already done, you'll need to average XXX characters per day to
hit the deadline." I envisioned a gnuplot table that showed
actual-characters-per-day against the shifting
average-characters-per-day.
I didn't make my deadline. I don't blame Org for that, but I think I
would have stood a better chance if org-log existed. :)
Eric
> 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-21 0:29 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
2014-10-21 0:34 ` Eric Abrahamsen [this message]
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
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=87zjcqz2f2.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.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 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).