From mboxrd@z Thu Jan 1 00:00:00 1970 From: Iannis Zannos Subject: SCHEDULED property behavior not compatible with habits? Confused: How to make this work? #orgmode Date: Sun, 29 Sep 2013 02:21:55 +0300 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e0160ce4e66f82d04e779de94 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41685) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VQ3pl-0004uX-UO for emacs-orgmode@gnu.org; Sat, 28 Sep 2013 19:21:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VQ3pk-00078Z-SW for emacs-orgmode@gnu.org; Sat, 28 Sep 2013 19:21:57 -0400 Received: from mail-ee0-x235.google.com ([2a00:1450:4013:c00::235]:37597) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VQ3pk-00078S-Jq for emacs-orgmode@gnu.org; Sat, 28 Sep 2013 19:21:56 -0400 Received: by mail-ee0-f53.google.com with SMTP id b15so1908668eek.40 for ; Sat, 28 Sep 2013 16:21:55 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: emacs-orgmode@gnu.org --089e0160ce4e66f82d04e779de94 Content-Type: text/plain; charset=ISO-8859-1 Hello, having tried out the "habits" module after studying the manual on TODOs and scheduling, I cannot make habits work. Reason: When I set the :SCHEDULED: property of a node with a repetition interval such as: <2013-09-27 Fri .+1d>, then changing the TODO status from TODO to DONE will 1. change the status back to TODO (so that the item stays scheduled for a next time) 2. change the date of SCHEDULED to one day after the date of completion of the task This is consistent with the description in the manual at 8.3.2 Repeated tasks, and makes sense. However, it interferes with habits, because it changes the date from which the tracking of the habit repetition of the task is being tracked. This means that this node disappears from the habit display in the agenda. Also, it undoes the configured logging mechanism (for example, note+timestamp for DONE state. Am I overseeing something? Surely it must be my mistake. I saw habits at work in the chat of Sacha Chua with Bastien Guerry ( http://sachachua.com/blog/2013/07/emacs-chat-sacha-chua-with-bastien-guerry/) and was quite impressed. But I could not repeat the same results as I saw on Sacha's screen. Cheers, Iannis Zannos --089e0160ce4e66f82d04e779de94 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Hello,=A0

having tried out the "habits" module after studying the manua= l on TODOs and scheduling, I cannot make habits work. Reason:=A0

When I set the :SCHEDULED: property of a node with a r= epetition interval such as: <2013-09-27 Fri .+1d>, then changing the = TODO status from TODO to DONE will=A0
  1. change the status back to TODO (so that the item stays scheduled for a next= time)
  2. change the date of SCHEDULED to one day after the date= of completion of the task
This is consistent with the description= in the manual at=A08.3.2 Repeated tasks, and makes sense. However, it inte= rferes with habits, because it changes the date from which the tracking of = the habit repetition of the task is being tracked. This means that this nod= e disappears from the habit display in the agenda. Also, it undoes the conf= igured logging mechanism (for example, note+timestamp for DONE state.=A0

Am I overseeing something? Surely it must b= e my mistake. I saw habits at work in the chat of Sacha Chua with Bastien G= uerry (http://sachachua.com/blog/2013/07/emacs-chat-sacha-chu= a-with-bastien-guerry/) and was quite impressed. But I could not repeat= the same results as I saw on Sacha's screen.=A0

Cheers,=A0

Iannis Zannos
--089e0160ce4e66f82d04e779de94--