From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Treat custom environment as verbatim on export Date: Sun, 24 May 2015 17:29:31 +0200 Message-ID: <878ucedmec.fsf@nicolasgoaziou.fr> References: <87fv6ntyiv.fsf@pank.eu> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33240) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YwXow-0005xm-JQ for emacs-orgmode@gnu.org; Sun, 24 May 2015 11:28:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YwXot-0007zi-Eo for emacs-orgmode@gnu.org; Sun, 24 May 2015 11:28:10 -0400 Received: from relay3-d.mail.gandi.net ([2001:4b98:c:538::195]:35120) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YwXot-0007za-8G for emacs-orgmode@gnu.org; Sun, 24 May 2015 11:28:07 -0400 In-Reply-To: <87fv6ntyiv.fsf@pank.eu> (rasmus@gmx.us's message of "Sat, 23 May 2015 11:48:40 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Rasmus Cc: emacs-orgmode@gnu.org Rasmus writes: > It's a special block, so e.g. org-latex-special-block. But contents is > already transcoded by the time in arrives to e.g. org-latex-special-block. > To the extend this should be fixed, one way would be to allow a raw option > to special blocks (also needed for e.g. #+{begin,end}_equation) and have > babel insert it as needed. I don't know how easy this is. I don't think a ":raw" option for special blocks is worth implementing. There are two types or "raw" contents: "protected raw" (i.e., verbatim contents) and "export-specific raw" (i.e., target language code). For the former, we already have example blocks (or fixed-width areas) and for the latter, export blocks. A third category exists, "multi-language raw", in which, I think, only the most trivial cases (those you never really need in practice) would fit. The OP wants special "protected raw" for LaTeX back-end. We could provide a special attribute for this, e.g., #+ATTR_LATEX: :environment "my-verbatim" #+BEGIN_EXAMPLE ... stuff... #+END_EXAMPLE But this is really only a shortcut for #+BEGIN_my-verbatim #+BEGIN_LATEX stuff #+END_LATEX #+END_my-verbatim WDYT? Regards,