emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Gustavo Barros <gusbrs.2016@gmail.com>
To: Kevin Liu <kevin@nivekuil.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Repeating task hourly
Date: Wed, 29 Jul 2020 12:15:18 -0300	[thread overview]
Message-ID: <87r1sufj3u.fsf@gmail.com> (raw)
In-Reply-To: <87a6zi5qgu.fsf@nivekuil.com>

Hi Kevin,

On Wed, 29 Jul 2020 at 11:46, Kevin Liu <kevin@nivekuil.com> wrote:

> On 29 July 2020 04:06, Gustavo Barros <gusbrs.2016@gmail.com> wrote:
>>
>> Kevin, how do you see an hourly repeater would work with org-habit's
>> consistency graph?  Or, more generally, what would be the purpose of 
>> an
>> hourly repeated habit task?
>
> An example of an hourly repeated habit task is exercise.  You might 
> want
> to stretch in the morning and then again at night.
>
> You raise a good point that the consistency graph isn't as useful as 
> it
> could be.  All it shows now is that the habit was done at least once 
> on
> that day.  I think this is still a little useful, if only to visually
> separate a habit from other tasks on the agenda.  It could be made 
> more
> useful by replacing the * with a count of the number of times the task
> was done that day, but that would be another patch.

I get why a task (exercising, taking medicine, etc) is usefully repeated 
a number of times a day, of course.  But a regular repeating task is 
perfectly fine for this.  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.

Anyway, you have replied just for me, off-list.  I presume you meant 
otherwise, and your point is relevant in the list, so I reincluded the 
CCs to it.

Best,
Gustavo.


  parent reply	other threads:[~2020-07-29 15:16 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 [this message]
2020-07-29 15:41           ` Kevin Liu
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=87r1sufj3u.fsf@gmail.com \
    --to=gusbrs.2016@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kevin@nivekuil.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).