From: Bernt Hansen <bernt@norang.ca>
To: Tommy Kelly <tommy.kelly@verilab.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Understanding habits - graph coloring of single missed day
Date: Mon, 03 Jan 2011 17:05:26 -0500 [thread overview]
Message-ID: <87ei8tr6c9.fsf@norang.ca> (raw)
In-Reply-To: <m2ipy5zr5k.fsf@verilab.com> (Tommy Kelly's message of "Mon, 03 Jan 2011 14:08:39 -0600")
Tommy Kelly <tommy.kelly@verilab.com> writes:
> Assuming I have the correct repeater syntax for a daily habit, what
> should the colored graph look like if I do the task consistently for a
> few days, then miss a day, then pick up the task again? What I expected
> to see was:
>
>
> - a set of GREEN cells (with asterisks)
> - a RED cell (no asterisk) for the missed day
> - more GREEN cells (again with asterisks).
>
> But what I actually see is
>
> - a set of GREEN cells (with *)
> - a YELLOW cell (no *) for the missed day
> - a RED cell (with *) for the day after the missed day
> - more GREEN cells (with *)
>
> Is that the way it's supposed to be? It doesn't seem right somehow.
I think that's right. The *'s mark the days you did the habit. As I
understand it the meaning of the colors is as follows:
BLUE: Done early (before the next repeat interval)
GREEN: Done on time
YELLOW: Will be late on the following day if not done on this date
RED: overdue
So a daily repeating task will always have today in yellow (since it'll
be late (red) if you don't do it today.) For a daily task any days
without a * are missed.
For habits that that can go a day or two (or longer) without requiring a
repeat the colors probably make more sense.
Regards,
Bernt
prev parent reply other threads:[~2011-01-03 22:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 20:08 Understanding habits - graph coloring of single missed day Tommy Kelly
2011-01-03 22:05 ` Bernt Hansen [this message]
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=87ei8tr6c9.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=tommy.kelly@verilab.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.