From: Bernt Hansen <bernt@norang.ca>
To: Tommy Kelly <tommy.kelly@verilab.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Understanding habits - repeat interval
Date: Mon, 03 Jan 2011 16:53:46 -0500 [thread overview]
Message-ID: <87ipy5r6vp.fsf@norang.ca> (raw)
In-Reply-To: <m2pqsdzrbg.fsf@verilab.com> (Tommy Kelly's message of "Mon, 03 Jan 2011 14:05:07 -0600")
Tommy Kelly <tommy.kelly@verilab.com> writes:
> I'm trying a first use of the habits tracking function but I'm not sure
> I understand the way they are set up. I have three questions. Here's the
> first.
>
> Is it possible to set up a daily habit -- that is, one that should be
> done at least every day and at most every day (as opposed to the
> "shaving" example in the manual where the at-most and at-least numbers
> are different). Suppose I want to shave every day. Is this correct:
>
> ** TODO Shave
> SCHEDULED: <2009-10-17 Sat .+1d>
This should work.
>
> I already tried the following but it gives an error:
>
> ** TODO Shave
> SCHEDULED: <2009-10-17 Sat .+1d/1d>
Recent versions of org-mode flag this as an error. So I just use the
first example you have for things that repeat daily (as habits)
,----
| if: Habit Shave deadline repeat period is less than or equal to scheduled (.+1d/1d)
`----
I'm not sure why equal is considered an error in this case. It breaks
agenda display completely for me until I edit the offending habit entry.
>
> The first seems to work but it's giving me a confusing bar chart (more
> on that later), so I wanted to ask in case the repeater is wrong.
Any repeater should be valid. (.+1d, ++1d, +1d)
Regards,
Bernt
prev parent reply other threads:[~2011-01-03 21:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 20:05 Understanding habits - repeat interval Tommy Kelly
2011-01-03 21:53 ` 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
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=87ipy5r6vp.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 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).