From: Kevin Liu <kevin@nivekuil.com>
To: Gustavo Barros <gusbrs.2016@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Repeating task hourly
Date: Wed, 29 Jul 2020 08:41:34 -0700 [thread overview]
Message-ID: <877dum5nwx.fsf@nivekuil.com> (raw)
In-Reply-To: <87r1sufj3u.fsf@gmail.com>
On 29 July 2020 08:15, Gustavo Barros <gusbrs.2016@gmail.com> wrote:
> Furthermore, considering the only thing org-habit does is to provide
> the consistency graph for the task, and if this does not really work
> for hourly repeaters, I still don't see the gain here. And there
> would be other ways, in my view more appropriate ones, to separate
> some tasks, if that's desired. IMHO, what you are proposing is just
> eliminating an error message which was deliberately placed there by
> the author, considering what org-habit is designed to do. But this is
> just an user speaking, take this as a data point.
The graph works for hourly repeaters in exactly the same way as it works
in all other cases. It illustrates whether the task was done on a given
day.
The gain is being able to use org-habit at all with hourly repeating
tasks. At the moment, this is unnecessarily precluded, and not even by
the error I removed; the actual error that pops up if you build the
agenda with an hourly habit is rather cryptic:
if: Invalid duration string: .+5h
As Kyle mentioned, I don't think authorial intent counts for a whole lot
here since the code was last touched in 2009, years before hourly
repeaters were added.
next prev parent reply other threads:[~2020-07-29 15:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 11:30 Repeating task hourly Kevin Liu
2020-07-27 11:40 ` Kevin Liu
2020-07-29 2:29 ` Kyle Meyer
2020-07-29 11:06 ` Gustavo Barros
[not found] ` <87a6zi5qgu.fsf@nivekuil.com>
2020-07-29 15:15 ` Gustavo Barros
2020-07-29 15:41 ` Kevin Liu [this message]
2020-07-29 16:29 ` Gustavo Barros
2020-07-30 15:25 ` Kevin Liu
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=877dum5nwx.fsf@nivekuil.com \
--to=kevin@nivekuil.com \
--cc=emacs-orgmode@gnu.org \
--cc=gusbrs.2016@gmail.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).