From: Charles Millar <millarc@verizon.net>
To: emacs-orgmode@gnu.org
Subject: Bug: State change not entered in corresponding TODO entry (resent with version info)
Date: Tue, 12 Jan 2016 14:11:55 -0500 [thread overview]
Message-ID: <56954FFB.5040009@verizon.net> (raw)
I group all of my TODO items in one file under one first level heading,
e.g.
* TODO'a
** TODO this is a test :CM:
DEADLINE: <2016-01-15 Fri>
:OTHERINFO:
:END:
Date Entered [2016-01-12 Tue 13:22]
** TODO this is another test :CM:
DEADLINE: <2016-01-20 Wed>
:OTHERINFO:
:END:
Date Entered [2016-01-12 Tue 13:36]
With point on the ** TODO this is another test and I change the state
for example to DONE (C-c C-t d) the state change is filed after the
first ** TODO and immediately above the "this is another test"
** TODO this is a test :CM:
DEADLINE: <2016-01-15 Fri>
:OTHERINFO:
:END:
Date Entered [2016-01-12 Tue 13:22]
** TODO this is a test :CM:
DEADLINE: <2016-01-15 Fri>
:OTHERINFO:
:END:
Date Entered [2016-01-12 Tue 13:22]
- State "DONE" from "TODO" [2016-01-12 Tue 13:38]
** DONE this ia another test :CM:
DEADLINE: <2016-01-20 Wed>
:OTHERINFO:
:END:
Date Entered [2016-01-12 Tue 13:36]
- State "DONE" from "TODO" [2016-01-12 Tue 13:38]
** DONE this is another test :CM:
DEADLINE: <2016-01-20 Wed>
:OTHERINFO:
:END:
Date Entered [2016-01-12 Tue 13:36]
I believe that that the state change should be (or it was in the past)
filed within the TODO item that was changed.
I tested this with a simple "* TODO something" headline and the state
change is entered above the * TODO.
GNU Emacs 24.4.1 (x86_64-pc-linux-gnu, GTK+ Version 3.14.5) of
2015-03-07 on trouble, modified by Debian
Org-mode version 8.3.3 (release_8.3.3-435-gb78a9b @
/usr/local/share/emacs/site-lisp/org-mode/lisp/)
Charlie Millar
next reply other threads:[~2016-01-12 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 19:11 Charles Millar [this message]
2016-01-12 20:32 ` Bug: State change not entered in corresponding TODO entry (resent with version info) 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=56954FFB.5040009@verizon.net \
--to=millarc@verizon.net \
--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).