emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Karl Voit <devnull@Karl-Voit.at>
To: emacs-orgmode@gnu.org
Subject: Re: habits don't get re-scheduled
Date: Sat, 12 Jan 2013 14:36:52 +0100	[thread overview]
Message-ID: <2013-01-12T14-31-47@devnull.Karl-Voit.at> (raw)
In-Reply-To: 8738y629nl.fsf@bzg.ath.cx

* Bastien <bzg@altern.org> wrote:
> Hi Karl,

Hi!

> Karl Voit <devnull@Karl-Voit.at> writes:
>
>> Another strange issue that I recognized today though: my habits do
>> not work any more: Whenever I mark an habit as DONE, it does not get
>> re-scheduled as is was before your recent changes. A CLOSED
>> time-stamp is added instead.
>>
>> Is there something I overlooked in the list of changes that I have
>> to adopt or do I face a bug?
>
> I tried to reproduce the issue but couldn't ... perhaps I need
> more info from your config file?   If you can go and bisect, that'd
> be great.  Thanks!

I bisected this issue. It resulted in:

,----
| 8f749c983493a010c4ae0437975c8cb63017c3f4 is the first bad commit
| commit 8f749c983493a010c4ae0437975c8cb63017c3f4
| Author: Bastien Guerry <bzg@altern.org>
| Date:   Mon Jan 7 12:33:57 2013 +0100
|
|     org-depend.el (org-depend-trigger-todo): Refresh effort text properties
|
|     * org-depend.el (org-depend-trigger-todo): Refresh effort text
|     properties.  Do not use `org-get-effort' for getting the
|     effort property value.
`----

I also have to add, that *Messages* shows following lines when I set
an habit to DONE when using a commit-ID that has the issue mentioned
above:

,----
| TODO state changed to DONE
| TODO state changed to TODO
| org-depend-trigger-todo: Symbol's function definition is void: org-refresh-effort-properties
| Note stored
`----

-- 
Karl Voit

  reply	other threads:[~2013-01-12 13:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08 11:31 Org-mode release 7.9.3 Bastien
2013-01-08 13:11 ` Rainer Stengele
2013-01-08 13:30   ` Bastien
2013-01-08 14:00     ` Rainer Stengele
2013-01-08 14:36       ` Bastien
2013-01-09 15:03     ` Inherited tags not visible in agenda (was: Org-mode release 7.9.3) Karl Voit
2013-01-09 17:11       ` Inherited tags not visible in agenda Bastien
2013-01-09 18:39         ` Karl Voit
2013-01-11 16:36       ` Bastien
2013-01-11 17:50         ` habits don't get re-scheduled (was: Inherited tags not visible in agenda) Karl Voit
2013-01-12  6:33           ` habits don't get re-scheduled Bastien
2013-01-12 13:36             ` Karl Voit [this message]
2013-01-12 14:08               ` Bastien
2013-01-12 21:49                 ` Karl Voit
2013-01-13 15:31                   ` J. David Boyd
2013-01-13 19:02                     ` Karl Voit
2013-01-08 16:45 ` Org-mode release 7.9.3 J. David Boyd
2013-01-08 17:02   ` J. David Boyd
2013-01-08 17:40     ` Bastien
2013-01-09 14:56       ` J. David Boyd
2013-01-09 15:04         ` Nick Dokos
2013-01-10  0:59           ` J. David Boyd
2013-01-09 15:39         ` J. David Boyd

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=2013-01-12T14-31-47@devnull.Karl-Voit.at \
    --to=devnull@karl-voit.at \
    --cc=emacs-orgmode@gnu.org \
    --cc=news1142@Karl-Voit.at \
    /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).