From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: #+INCLUDE: myfile.html html does not include /literally/; Org processes Date: Sun, 01 Jun 2014 10:31:31 +0200 Message-ID: <87bnudf2u4.fsf@gmail.com> References: <538AA6B8.40604@gmail.com> <8761kl12w9.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51025) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wr1AR-00031R-8r for emacs-orgmode@gnu.org; Sun, 01 Jun 2014 04:31:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Wr1AM-0005mo-Ja for emacs-orgmode@gnu.org; Sun, 01 Jun 2014 04:30:59 -0400 Received: from mail-we0-x232.google.com ([2a00:1450:400c:c03::232]:49522) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wr1AM-0005m9-DI for emacs-orgmode@gnu.org; Sun, 01 Jun 2014 04:30:54 -0400 Received: by mail-we0-f178.google.com with SMTP id u56so3745117wes.37 for ; Sun, 01 Jun 2014 01:30:53 -0700 (PDT) In-Reply-To: <8761kl12w9.fsf@Rainer.invalid> (Achim Gratz's message of "Sun, 01 Jun 2014 09:53:58 +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: Achim Gratz Cc: emacs-orgmode@gnu.org Hello, Achim Gratz writes: > That's not yet possible. The following patch would implement it, but I > guess there are a few things that need to be discussed before this gets > official, if at all. I haven't given it much testing either. > > From 425b53146b99b1dd9b9b5d9b96e950dfea81835c Mon Sep 17 00:00:00 2001 > From: Achim Gratz > Date: Sun, 1 Jun 2014 09:49:48 +0200 > Subject: [PATCH] ox: implement "wrap" for #+INCLUDE > > * lisp/ox.el (org-export-expand-include-keyword): Implement additional > "wrap" parameter for including files literally, wrapped in an > appropriate block (usually an export block). The contents of the > file gets included literally. Thanks for the patch. However, I'd rather not allow arbitrary blocks around included files, as it can be the source of some headache (e.g., a quote block around an Org file containing a headline). Also we don't really need it since most use-cases are already supported. Actually, I think there are two possible ways to handle this: 1. Add a new "export" (or something else) parameter which will wrap file contents within an export block relative to the current back-end. Unfortunately, this will not work for exotic back-ends that do not provide such a block (:export-block property in its definition). We can always fallback to an example block in this case, though. 2. Extend "src" syntax to allow Babel parameters after the language. E.g., #+INCLUDE: "file.html" src html :results html WDYT? Regards, -- Nicolas Goaziou