emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dan LaManna <dan.lamanna@gmail.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Navigating from agenda causes incorrect expansion of children
Date: Tue, 18 Mar 2014 22:10:35 -0400	[thread overview]
Message-ID: <5328FC9B.3040205@gmail.com> (raw)

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

Not sure if this is a feature or a bug, but those on #org-mode prompted 
me to post it.

GNU Emacs 24.3.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.10)
Org version 8.2.5c

If you take the following minimal example of an org file:
* A
** B
*** TODO C
*** D
*** E

And navigate to TODO C from an agenda buffer this will be the 
*displayed* text:
* A
** B
*** TODO C
*** D...

Leaving it to appear that D has children, when it in fact has a sibling 
that's been hidden.

Is this some type of custom variable I'm missing, or is this working as 
intended - or is this truly a bug?

May be worth mentioning, myself and others in #org-mode have noticed 
this happening in other contexts, however this was the only reproducible 
method.

- dan lamanna


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

             reply	other threads:[~2014-03-19  2:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-19  2:10 Dan LaManna [this message]
2014-03-19 10:01 ` Navigating from agenda causes incorrect expansion of children Bastien
2014-03-19 20:09   ` Samuel Wales
2014-03-19 23:05     ` Bastien
2014-03-19 23:30       ` Samuel Wales
2014-03-19 23:36         ` Bastien
2014-03-20  0:13           ` Samuel Wales
2014-03-20  7:11             ` Bastien
2014-03-20 20:09               ` Samuel Wales
2014-03-20 21:59                 ` Bastien
2014-03-21 21:25                   ` Samuel Wales
2014-03-21 22:09                     ` Bastien
2014-03-21 22:58                       ` Samuel Wales
2014-03-21 23:52                         ` Bastien
2014-03-31  5:43                           ` 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=5328FC9B.3040205@gmail.com \
    --to=dan.lamanna@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).