From mboxrd@z Thu Jan  1 00:00:00 1970
From: Robert Horn <rjhorn@alum.mit.edu>
Subject: Re: Habit setup help needed
Date: Thu, 20 Sep 2012 10:40:21 -0400
Message-ID: <m3mx0kn4fe.fsf@quad.robs.office>
References: <m3392fhvcx.fsf@quad.robs.office>
	<87vcf9t1bc.fsf@mean.albasani.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([208.118.235.92]:47340)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rjhorn@alum.mit.edu>) id 1TEhvV-0007K2-HR
	for emacs-orgmode@gnu.org; Thu, 20 Sep 2012 10:40:31 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rjhorn@alum.mit.edu>) id 1TEhvT-0005Ku-Tf
	for emacs-orgmode@gnu.org; Thu, 20 Sep 2012 10:40:25 -0400
Received: from mailbackend.panix.com ([166.84.1.89]:41553)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rjhorn@alum.mit.edu>) id 1TEhvT-0005Iu-Qh
	for emacs-orgmode@gnu.org; Thu, 20 Sep 2012 10:40:23 -0400
In-Reply-To: <87vcf9t1bc.fsf@mean.albasani.net>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Memnon Anon <gegendosenfleisch@googlemail.com>, emacs-orgmode@gnu.org

Memnon Anon <gegendosenfleisch@googlemail.com> writes:
>
> I think the consistency bar is only fully functional with timestamps 
> of the format <2012-09-13 Do .+7d/10d> : You need a minimum/maximum range.
>

Thank you.  That was the clue I needed.  I hadn't made the connection
between schedule repeat intervals and deadlines in habits.  So I was expecting
task  deadlines to cover that.

I suggest adding the following to item 5. in the habit documentation:

  A weekly report that must be filed during the following work week
  could be described with "SCHEDULED: <2012-09-24 Mon +1w/12d>". 

Have I understood this correctly?  It works for the habits that I'm
testing, but I haven't figured out the code to be sure that this covers
the edge cases properly. 

Assuming that this is correct, perhaps the info section on dates and
times should note that the habit option extends the scheduled time
notation.  That will catch folks who go to that section directly.

Alternatively, a more radical change would be to change habits to use
scheduled and deadline in the same sense that they are used elsewhere:
scheduled means should start at this time, deadline means should
complete at this time.  That would affect all current users.  Is there
an extra capability that this notation adds?

R Horn
rjhorn@alum.mit.edu