From: swflint@flintfam.org (Samuel W. Flint)
To: emacs-orgmode@gnu.org
Subject: Re: Bug: Habits will not correctly reset timestamp [8.3.2 (release_8.3.2-570-gc17fcc @ /home/swflint/.emacs.d/org-mode/lisp/)]
Date: Thu, 28 Jan 2016 11:24:46 -0500 [thread overview]
Message-ID: <87h9hx7ju9.fsf@turing.flintfam.org> (raw)
In-Reply-To: <877fiu3zb6.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Thu, 28 Jan 2016 09:04:13 +0100")
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
:: Nicolas Goaziou writes:
NG> Hello, swflint@flintfam.org (Samuel W. Flint) writes:
>> See my previous bug report. This still happens.
>>
>> If I have a heading like so:
>>
>> * TODO Something SCHEDULED: <2016-01-17 Sun .+1w/2w> :PROPERTIES:
>> :STYLE: habit :END:
>>
>> And execute C-c C-t d on the heading, the following appears:
>>
>> * TODO Something :PROPERTIES: :STYLE: habit :END:
>>
>> This is incorrect behavior, and I'm unable to use org-habits
>> correctly.
NG> I cannot reproduce it. With -Q, I get
NG> * TODO Something SCHEDULED: <2016-02-04 jeu. .+1w/2w> :PROPERTIES:
NG> :STYLE: habit :LAST_REPEAT: [2016-01-28 jeu. 09:03] :END: - State
NG> "DONE" from "TODO" [2016-01-28 jeu. 09:03]
With -Q, I still have the same problem. It is not a top level heading,
but even as a top level heading, this doesn't happen. The SCHEDULED
line is removed, rather than updated.
Thanks,
Sam
NG> Regards,
NG> -- Nicolas Goaziou
--
Samuel W. Flint
4096R/266596F4
(9477 D23E 389E 40C5 2F10 DE19 68E5 318E 2665 96F4)
(λs.s s) λs.s s
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2016-01-28 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 20:56 Bug: Habits will not correctly reset timestamp [8.3.2 (release_8.3.2-570-gc17fcc @ /home/swflint/.emacs.d/org-mode/lisp/)] Samuel W. Flint
2016-01-28 8:04 ` Nicolas Goaziou
2016-01-28 16:24 ` Samuel W. Flint [this message]
2016-01-29 13:28 ` Nicolas Goaziou
2016-01-30 1:46 ` Samuel W. Flint
2016-01-30 23:17 ` Nicolas Goaziou
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=87h9hx7ju9.fsf@turing.flintfam.org \
--to=swflint@flintfam.org \
--cc=emacs-orgmode@gnu.org \
/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).