From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: BUG: Org subtree immediately following a #+RESULTS: line gets deleted [org master]
Date: Mon, 27 Nov 2017 23:35:33 +0100 [thread overview]
Message-ID: <877eubs62y.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAFyQvY0RkOogBm0XkyBYP+5_u4msXUhjT9BWitFu=amDoau5Sw@mail.gmail.com> (Kaushal Modi's message of "Mon, 27 Nov 2017 21:28:19 +0000")
Hello,
Kaushal Modi <kaushal.modi@gmail.com> writes:
> Hello,
>
> I believe this has to do with the recent change to #+RESULTS removal
> without blank line [1]
>
> Here's a MWE:
>
> =====
>
> #+TITLE: The disappearing act
>
> * Heading 1
>
> #+BEGIN_SRC emacs-lisp
> (message "Hello")
> #+END_SRC
>
>
> #+RESULTS:
> * Heading 2
> Lorem ipsum dolor sit amet, consectetur adipiscing elit. Quisque et
> quam metus. Etiam in iaculis mi, sit amet pretium magna. Donec ut dui
> mi. Maecenas pharetra sapien nunc, ut mollis enim aliquam quis. Nam at
> ultricies metus. Nulla tempor augue in vestibulum tristique. Phasellus
> volutpat pharetra metus quis suscipit. Morbi maximus sem dolor, id
> accumsan ipsum commodo non.
> * Heading 3
> =====
>
> With point on the code block, do C-c C-c, allow running of that elisp
> snippet, and the * Heading 2 subtree will get wiped out! (git just saved me
> from losing data from that Org file).
>
> After C-c C-c, you will get:
>
> =====
>
> #+TITLE: The disappearing act
>
> * Heading 1
>
> #+BEGIN_SRC emacs-lisp
> (message "Hello")
> #+END_SRC
>
> #+RESULTS:
> : Hello
> * Heading 3
> =====
Ouch! Fixed. Thank you.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-11-27 22:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 21:28 BUG: Org subtree immediately following a #+RESULTS: line gets deleted [org master] Kaushal Modi
2017-11-27 22:35 ` Nicolas Goaziou [this message]
2017-11-27 23:04 ` Kaushal Modi
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=877eubs62y.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=kaushal.modi@gmail.com \
/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).