From: Bernt Hansen <bernt@norang.ca>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: please read: bug when marking tasks done
Date: Tue, 08 Jan 2019 09:29:21 -0500 [thread overview]
Message-ID: <87y37v5ike.fsf@norang.ca> (raw)
In-Reply-To: <87muobcur7.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Tue, 08 Jan 2019 11:24:12 +0100")
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Anyway, I don't really have any other idea besides dropping the repeater
> part from automatically inserted inactive time stamps.
When I unschedule (and log) a habit I don't want to lose the detail
about the repeat interval. My workaround for this is to break the
timestamp by adding a ',' after the '[' in the timestamp so marking it
DONE actually works.
** DONE Weekly Review 2018 [0/16]
CLOSED: [2019-01-08 Tue 09:19]
:PROPERTIES:...
:LOGBOOK:
- State "DONE" from "TODO" [2019-01-08 Tue 09:19]
- Not scheduled, was "[,2019-01-07 Mon ++7d/14d]" on [2019-01-08 Tue
09:18]
Marking this task done is also pretty slow - taking 25 seconds.
The task has 233 lines, 2549 words, and 12993 characters.
partial elp-results for this task below
org-todo 1 25.33 25.33
org-self-insert-command 1 25.33 25.33
org-checklist 1 25.124 25.124
org-reset-checkbox-state-subtree 1 25.124 25.124
org-reset-checkbox-state-maybe 1 25.124 25.124
org-update-checkbox-count 1 24.945 24.945
org-update-checkbox-count-maybe 1 24.945 24.945
org-element-at-point 1548 24.870999999 0.0160665374
org-element-context 1541 24.868999999 0.0161382219
org-element--parse-to 1544 24.718999999 0.0160097150
org-element--current-element 3109 22.070999999 0.0070990672
org-element-example-block-parser 1537 19.664999999 0.0127944046
org-unescape-code-in-string 1537 13.604000000 0.0088510084
org-element-paragraph-parser 1544 1.7799999999 0.0011528497
org-fast-todo-selection 1 0.201 0.201
...
Regards,
Bernt
next prev parent reply other threads:[~2019-01-08 14:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-06 0:13 please read: bug when marking tasks done cesar mena
2019-01-06 23:49 ` Nicolas Goaziou
2019-01-07 14:52 ` Bernt Hansen
2019-01-07 15:20 ` cesar mena
2019-01-08 10:24 ` Nicolas Goaziou
2019-01-08 14:29 ` Bernt Hansen [this message]
2019-01-08 20:07 ` cesar mena
2019-01-09 22:50 ` Nicolas Goaziou
2019-01-10 14:15 ` cesar mena
2019-01-12 11:24 ` Nicolas Goaziou
2019-01-12 14:23 ` cesar mena
2019-01-12 19:37 ` Samuel Wales
2019-01-12 21:02 ` Samuel Wales
2019-01-13 15:00 ` Nicolas Goaziou
2019-01-13 20:16 ` Nicolas Goaziou
2019-01-13 21:52 ` Samuel Wales
2019-01-15 14:24 ` Bernt Hansen
2019-01-15 16:43 ` cesar mena
2019-01-15 23:11 ` Samuel Wales
2019-01-15 23:18 ` Samuel Wales
2019-01-27 21:08 ` Nicolas Goaziou
2019-01-29 14:58 ` Robert Horn
2019-01-30 12:22 ` cesar mena
2019-01-30 21:52 ` Nicolas Goaziou
2019-01-31 10:25 ` cesar mena
2019-01-31 23:17 ` Samuel Wales
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=87y37v5ike.fsf@norang.ca \
--to=bernt@norang.ca \
--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).