From: Bastien <firstname.lastname@example.org>
To: Luca Ferrari <email@example.com>
Cc: firstname.lastname@example.org, Marcin Borkowski <email@example.com>
Subject: Re: some key sequence transform my text in outline
Date: Thu, 18 Apr 2013 12:24:27 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <CAKoxK+5QJjzHf5a8DkePJSmQPGpaed6U4-59HGxSoZf8vRaqig@mail.gmail.com> (Luca Ferrari's message of "Wed, 3 Apr 2013 08:24:44 +0200")
Luca Ferrari <email@example.com> writes:
> Apparently I found the sequence that lead to the problem: I opened a
> #+begin_src on a line and then pressed TAB on such line. This folded
> the following text until a new #+end_src is found, masking whole
> sections. The problem is that this is no more able to be expanded.
> However, editing the text file externally and removing some text after
> the #+begin_src (in particular a table) solved the problem.
> I'm investigating more...
It would be really nice to have a command to check that no #+begin_src
contains a headline, as this can confuse visibility cycling a lot,
among other things.
prev parent reply other threads:[~2013-04-18 10:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 12:22 some key sequence transform my text in outline Luca Ferrari
2013-03-27 12:39 ` Marcin Borkowski
2013-04-03 6:24 ` Luca Ferrari
2013-04-18 10:24 ` Bastien [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).