From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Michal Rus <m@michalrus.com>
Cc: "Rafał Babinicz" <kmicu@tuta.io>, emacs-orgmode@gnu.org
Subject: Re: Dr Wozniak’s tasklist implementation
Date: Sun, 29 Jan 2017 16:22:18 -0500 [thread overview]
Message-ID: <m2r33lsgs5.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <CAH=q+8L6ujDU3eMtxKra8ZKjneqnTNtKfUnUefvV9b5J0cku4g@mail.gmail.com>
I do not know of anything like this, but it should not be difficult to
implement. You could store $ and time as properties in a headline, and
then write a custom sort function for use with org-sort-entries that
computes the priority and sorts in the direction you want. I do not know
how you would integrate that into the agenda, but I assume it is
possible.
Michal Rus writes:
> Hello!
>
> I’d like to start using dr Wozniak’s tasklist idea [1] in Org. He’s
> the original author of spaced repetition and SuperMemo.
>
> It’s about assigning values ($) and time (hrs) to each task. Then,
> priorities ($ divided by hrs) can be calculated, and then you do the
> tasks with the highest priority; effectively, spending your time in
> the most valuable way. (That is if you assign the value and time
> correctly, but it can be learned.)
>
> Is there anything like that implemented? I couldn’t find anything.
>
> If not, how hard would it be? Where would it be best to start?
>
> Thank you!
>
> [1] https://www.supermemo.com/articles/tasklists.htm
--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
next prev parent reply other threads:[~2017-01-29 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-29 15:10 Dr Wozniak’s tasklist implementation Michal Rus
2017-01-29 21:22 ` John Kitchin [this message]
2017-01-29 22:19 ` Bob Newell
2017-02-02 0:52 ` Bob Newell
2017-01-30 7:38 ` Ramon Diaz-Uriarte
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=m2r33lsgs5.fsf@andrew.cmu.edu \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=kmicu@tuta.io \
--cc=m@michalrus.com \
/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.