From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Marcus Zibrowius <marcus.zibrowius@hhu.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Basic visibility cycling bug in 8.3.6
Date: Sat, 15 Oct 2016 22:25:13 +0200 [thread overview]
Message-ID: <87lgxp2wd2.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <1476544932.2521.17.camel@XPS12> (Marcus Zibrowius's message of "Sat, 15 Oct 2016 17:22:12 +0200")
Hello,
Marcus Zibrowius <marcus.zibrowius@hhu.de> writes:
> In this version, visibility cycling does not work as expected. Consider
> the following three-line example file:
>
> * a
> ** b
> ** c
>
> Consider the following sequence of commands:
> 1. Place cursor on the letter b.
> 2. In the menu, choose Org > Refresh/Reload > Refresh setup current
> buffer.
Note that you are leaving, on purpose, point in an invisible part of the
document.
> (I do not know how to access this command directly).
> 3. Press TAB on your keyboard.
>
> If I do this in org-mode 8.3.6, my buffer looks as follows:
>
> * a
> ** b
> ...
>
> In this minimalistic example, pressing TAB once more will bring back the
> line with the c, but in more complex examples, some parts of the buffer
> seem to "get lost". Moreover, I often find my files garbled like this
> when I open them from the agenda.
You can reveal text around point with C-c C-r (or even C-u C-c C-r). See
`org-reveal' for details.
By the way, Org 9.0 (yet to be released) contains a variable to control
this: `org-show-context-detail'. You may want to update Org.
> If I apply the above sequence of commands using my built-in org-mode
> 7.9.3, everything is fine.
I can reproduce the same with Org 7.9.3.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2016-10-15 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-15 15:22 Basic visibility cycling bug in 8.3.6 Marcus Zibrowius
2016-10-15 20:25 ` Nicolas Goaziou [this message]
[not found] ` <1476597091.2755.18.camel@XPS12>
2016-10-17 6:42 ` 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=87lgxp2wd2.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=marcus.zibrowius@hhu.de \
/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).