emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Mark Edgington <edgimar@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Bug: todo states not logged to drawer when using narrowed indirect buffer [8.3beta (release_8.3beta-1203-g93cc5f) ]
Date: Sat, 06 Jun 2015 09:16:24 +0200	[thread overview]
Message-ID: <87iob1johj.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAMsBe8rHVPFEKf+QC9U96YuvFu51ZzD7DoYp94KNpxHAiUPGsQ@mail.gmail.com> (Mark Edgington's message of "Thu, 4 Jun 2015 15:23:54 -0400")

Hello,

Mark Edgington <edgimar@gmail.com> writes:

> To reproduce this bug, do the following:
>
> 1.  edit / open the following org file:
>
>     #+TODO: TODO(t) WAIT(w!) | DONE(d!) CANCELED(c!)
>     #+STARTUP: logdrawer
>     * testing A
>     some stuff
>     * testing B
>
> 2.  execute (org-tree-to-indirect-buffer) on the 'testing A' headline
>
> 3.  go to the end of the indirect buffer, and add a new headline.  for example:
>
>     * testing C
>
> 4. change the TODO state of this new headline to TODO, and then to WAIT.
>
> You should now notice that a drawer was created in the initial
> (non-indirect) buffer, but is not visible in the indirect buffer.

This is a consequence of the narrowing in the indirect buffer: The
insertion point is not visible there. You could, for example, insert
a new line below the new headline to solve it.

> Furthermore, the logged state change appears *above* the drawer, and
> not inside it.

This should be fixed in 9fd317b1b00aec03430824b07310cb7b27d38cf8. Thank
you.

Regards,

-- 
Nicolas Goaziou

      reply	other threads:[~2015-06-06  7:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04 19:23 Bug: todo states not logged to drawer when using narrowed indirect buffer [8.3beta (release_8.3beta-1203-g93cc5f) ] Mark Edgington
2015-06-06  7:16 ` Nicolas Goaziou [this message]

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=87iob1johj.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=edgimar@gmail.com \
    --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).