Re: Question about todo subheadings and logbook

[Keith M Swartz <oneroadkms@gmail.com>]

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

I was creating the sub-heading from the exact same spot where I stopped
typing and hit C-c C-t. Didn't move the cursor, just went straight from one
step to the next.

After step

Here is what that set of steps created for me:

* PEND First item
:LOGBOOK:
- State "PEND"       from "TODO"       [2015-09-04 Fri 13:23]
:END:
*** PEND Second item
:LOGBOOK:
- State "PEND"       from "TODO"       [2015-09-04 Fri 13:23]
- State "TODO"       from              [2015-09-04 Fri 13:23]
- State "TODO"       from              [2015-09-04 Fri 13:22]
:END:

Step-by-step -- after step 1 [note: the logbook is collapsed initially, but
I expanded it here to show the contents. Expanding the logbook before
creating a sub-item may alter the results; I haven't tried that.]

* TODO First item
:LOGBOOK:
- State "TODO"       from              [2015-09-04 Fri 13:25]
:END:

after step 2:

* TODO First item
*** TODO Second item
:LOGBOOK:
- State "TODO"       from              [2015-09-04 Fri 13:26]
- State "TODO"       from              [2015-09-04 Fri 13:25]
:END:

Looks like our experiences already differ. (BTW, are you on the same org
version?)

after step 3:

* TODO First item
*** PEND Second item
:LOGBOOK:
- State "PEND"       from "TODO"       [2015-09-04 Fri 13:26]
- State "TODO"       from              [2015-09-04 Fri 13:26]
- State "TODO"       from              [2015-09-04 Fri 13:25]
:END:

And after step 4, it's as you saw above.

Keith


On Fri, Sep 4, 2015 at 12:38 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:

> Keith M Swartz <oneroadkms@gmail.com> writes:
>
> > Here is an example to reproduce some questionable results:
> >
> > 0. Create a set of TODO labels, like so:
> > #+SEQ_TODO: TODO(!) PEND(!) DONE(!)
> >
> > 1. Create an item, make it a todo. (Creates a logbook.)
>
> OK.
>
> > 2. Create a subheading. (Alt-Enter, shift-right)
>
> From where?
>
> > Make it a todo. (This adds a line to the logbook saying the state
> > changed to TODO, even though the previous line says the state already
> > is TODO. You can't tell which state changed.)
> >
> > 3. Cycle the state on your sub-todo to PEND. (Changes the state in the
> > logbook.)
> >
> > 4, Go back to the main heading and cycle the state to PEND. (This creates
> > ANOTHER logbook right underneath the heading showing the state change.
> The
> > original record for when it was marked TODO is in the other logbook, but
> > there are two such entries, and it's not obvious which one is which. You
> > could probably infer logically that the older entry is for the main
> > heading, but if states keep going back and forth, you'll lose track
> > quickly.)
>
> I cannot reproduce this. It creates the following document:
>
>   #+SEQ_TODO: TODO(!) PEND(!) DONE(!)
>
>   * PEND test
>     :LOGBOOK:
>     - State "PEND"       from "TODO"       [2015-09-04 ven. 21:37]
>     - State "TODO"       from              [2015-09-04 ven. 21:33]
>     :END:
>
>   ** PEND test2
>      :LOGBOOK:
>      - State "PEND"       from "TODO"       [2015-09-04 ven. 21:35]
>      - State "TODO"       from              [2015-09-04 ven. 21:34]
>      :END:
>
>
> Regards,
>



-- 

Keith M Swartz
oneroadkms@gmail.com

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