emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: Results with #+begin_example/#+end_example don't get overwritten
Date: Wed, 29 Nov 2017 19:10:31 +0100	[thread overview]
Message-ID: <87zi75neg8.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAFyQvY2vVV7v97Z7bv1rwzTLgHioOj=a0MxYXKbeoHdZFzCAKw@mail.gmail.com> (Kaushal Modi's message of "Tue, 28 Nov 2017 23:24:56 +0000")

Hello,

Kaushal Modi <kaushal.modi@gmail.com> writes:

> No, I wasn't suggesting a use case where someone writes the #+RESULTS:
> contents manually.
>
> Here's what can happen though:
>
> A user could have this to begin with:

[...]

> Then for whatever reason, they choose to delete the RESULTS manually.. and
> the blank line after that too!

IMO, this is still a manual operation on RESULTS keyword.

> That's why I proposed earlier to wrap the Org generated results in
> something like #+begin_results/#+end_results.

I think this would add too much cruft in the document.

> The current behavior is risky, or at least should somehow be
> documented.

Documentation can certainly help. I wouldn't qualify it as risky
however. In any case, it not riskier than the many other ways to fumble
in Org.

Regards,

-- 
Nicolas Goaziou

      reply	other threads:[~2017-11-29 18:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-28 21:58 Results with #+begin_example/#+end_example don't get overwritten Kaushal Modi
2017-11-28 22:07 ` Kaushal Modi
2017-11-28 22:36   ` Nicolas Goaziou
2017-11-28 22:45     ` Kaushal Modi
2017-11-28 23:16       ` Nicolas Goaziou
2017-11-28 23:24         ` Kaushal Modi
2017-11-29 18:10           ` Nicolas Goaziou [this message]

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=87zi75neg8.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).