emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Iannis Zannos <zannos@gmail.com>
To: Marcin Borkowski <mbork@wmi.amu.edu.pl>
Cc: emacs-orgmode@gnu.org
Subject: Re: SCHEDULED property behavior not compatible with habits? Confused: How to make this work? #orgmode
Date: Sun, 29 Sep 2013 03:08:24 +0300	[thread overview]
Message-ID: <CAEC5Jk+Qg6fBQHYt=Latr0Pubx-raS83HyGkvCxKfBrEYizafw@mail.gmail.com> (raw)
In-Reply-To: <20130929012947.3a3652c8@aga-netbook>

[-- Attachment #1: Type: text/plain, Size: 2119 bytes --]

Hello Marcin
Thanks, for the answer.
(setq org-habit-show-habits-only-for-today nil)
did the trick.
Perhaps this should go into the manual ...

Best,
Iannis Z.


On Sun, Sep 29, 2013 at 2:29 AM, Marcin Borkowski <mbork@wmi.amu.edu.pl>wrote:

> Dnia 2013-09-29, o godz. 02:21:55
> Iannis Zannos <zannos@gmail.com> napisał(a):
>
> > 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
>
> Tip 1: try setting org-habit-show-habits-only-for-today to nil (or
> waiting until tomorrow;)).
>
> Tip 2: it seems you mustn't track changes /into/ a TODO state, only
> into DONE.  See note at the bottom here:
> http://mbork.pl/2013-09-23_Automatic_insertion_of_habit_templates_%28en%29
>
> Hth,
>
> --
> Marcin Borkowski
> http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
> Adam Mickiewicz University
>
>

[-- Attachment #2: Type: text/html, Size: 3215 bytes --]

      reply	other threads:[~2013-09-29  0:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-28 23:21 SCHEDULED property behavior not compatible with habits? Confused: How to make this work? #orgmode Iannis Zannos
2013-09-28 23:29 ` Marcin Borkowski
2013-09-29  0:08   ` Iannis Zannos [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='CAEC5Jk+Qg6fBQHYt=Latr0Pubx-raS83HyGkvCxKfBrEYizafw@mail.gmail.com' \
    --to=zannos@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mbork@wmi.amu.edu.pl \
    /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).