From: Luca Ferrari <firstname.lastname@example.org>
To: Marcin Borkowski <email@example.com>
Subject: Re: some key sequence transform my text in outline
Date: Wed, 3 Apr 2013 08:24:44 +0200 [thread overview]
Message-ID: <CAKoxK+5QJjzHf5a8DkePJSmQPGpaed6U4-59HGxSoZf8vRaqig@mail.gmail.com> (raw)
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...
On Wed, Mar 27, 2013 at 1:39 PM, Marcin Borkowski <firstname.lastname@example.org> wrote:
> Dnia 2013-03-27, o godz. 13:22:47
> Luca Ferrari <email@example.com> napisał(a):
>> I cannot understand exactly what I type, but this is what happened
>> twice. I was editing in the middle of a document, in particular
>> within a "~" block with a src block on the next line, as in the
>> I was editing ~here~
>> #+begin_src shell
>> Now, with some key sequence Org eated all the text below the cursor
>> position, transforming it into an outline block and therefore showing
>> me three dots. The problem is that I'm unable to expand it anymore
>> with TAB, and moreover I cannot delete it without killing the whole
>> outline itself. I'm sure I've not pressed the SHIFT+TAB sequence, that
>> apparently does the same but allows me to expand the outline, while
>> the one I'm getting is not expandable in the ordinary way.
>> I know this is not a detailed explaination, but I don't understand
>> exactly what I (wrongly) activated.
>> Any suggestion?
> C-h l (or M-x view-lossage)
> Marcin Borkowski
> Adam Mickiewicz University
next prev parent reply other threads:[~2013-04-03 6: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 [this message]
2013-04-18 10:24 ` Bastien
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).