emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Sebastien Vauban
	<public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: Source block processing changes
Date: Tue, 06 Nov 2012 11:00:55 +0100	[thread overview]
Message-ID: <87d2zr9hk8.fsf@gmail.com> (raw)
In-Reply-To: <80fw4n6oi3.fsf@somewhere.org> (Sebastien Vauban's message of "Tue, 06 Nov 2012 10:59:16 +0100")



Hello,

"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:

> That's normal with raw results: as I wrote it in
> http://lists.gnu.org/archive/html/emacs-orgmode/2012-09/msg01273.html, as
> there are *no obvious markers to delimit the results* in the Org mode file,
> there is no way to know where raw results begin or end: raw results *cannot be
> removed* [NOR UPDATED] from the buffer.

The sole purpose of raw results is to allow inserting an headline (I
mean a real headline, not comma protected) in the buffer, because
headlines cannot be contained in anything else than headlines.

If the generated code doesn't contain an headline, you don't need raw
results.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2012-11-06 10:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-05 16:56 Source block processing changes Ista Zahn
2012-11-05 17:25 ` Nicolas Goaziou
2012-11-05 18:45   ` Ista Zahn
2012-11-06  9:59     ` Sebastien Vauban
2012-11-06 10:00       ` Nicolas Goaziou [this message]
2012-11-06 18:53       ` Achim Gratz
2012-11-06 13:22 ` Eric Schulte
2012-11-06 14:51   ` Ista Zahn
2012-11-06 16:44     ` Nicolas Goaziou
2012-11-06 17:06       ` Ista Zahn
2012-11-06 17:16         ` Nicolas Goaziou
2012-11-06 17:45           ` Ista Zahn
2012-11-06 17:48   ` Ista Zahn
2012-11-06 18:30     ` Ista Zahn

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=87d2zr9hk8.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
    --cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org \
    /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).