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: Two modifications for source blocks processing (will be in 7.9.2)
Date: Wed, 26 Sep 2012 13:57:47 +0200 [thread overview]
Message-ID: <87wqzh8090.fsf@gmail.com> (raw)
In-Reply-To: <80haql8afw.fsf@somewhere.org> (Sebastien Vauban's message of "Wed, 26 Sep 2012 10:17:39 +0200")
Hello,
"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
> Why don't we have anymore "#+begin/end_org" blocks while we still have
> "#+begin_html" and "#+begin_LaTeX" blocks? Org as the language seemed normal
> to insert blocks in Org-syntax.
#+begin_latex (like #+begin_html, #+begin_ascii, #+begin_md...) are
"export blocks", which basically means "insert contents as-is in output
from matching export back-end, ignore everything in other back-ends.".
They are relative to export back-ends, not languages. And there's no Org
back-end so far. So, they do not make much sense for now.
On the other hand, when you want to write in a foreign language, you use
#+begin_src blocks.
> Will ":RESULTS:" drawers be included by default, to mimic the current support
> of "#+begin/end_org" blocks?
In the new export engine, every drawer (excepted property drawer) is
included by default.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2012-09-26 12:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 7:44 Two modifications for source blocks processing (will be in 7.9.2) Bastien
2012-09-26 8:17 ` Sebastien Vauban
2012-09-26 9:09 ` Bastien
[not found] ` <1348655499.WXHGMQZGWMUF@spammotel.com>
2012-09-26 11:06 ` Bastien
2012-09-26 11:57 ` Nicolas Goaziou [this message]
2012-09-26 16:28 ` Thomas S. Dye
2012-09-26 20:20 ` Sebastien Vauban
2012-09-26 20:47 ` Thomas S. Dye
2012-09-26 20:51 ` Eric Schulte
2012-09-26 21:54 ` Bastien
2012-09-27 23:28 ` Thomas S. Dye
2012-09-27 5:34 ` Achim Gratz
2012-09-27 8:07 ` Bastien
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=87wqzh8090.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).