From mboxrd@z Thu Jan 1 00:00:00 1970 From: Achim Gratz Subject: Re: #+INCLUDE: myfile.html html does not include /literally/; Org processes Date: Sun, 01 Jun 2014 12:23:21 +0200 Message-ID: <87sinpylly.fsf@Rainer.invalid> References: <538AA6B8.40604@gmail.com> <8761kl12w9.fsf@Rainer.invalid> <87bnudf2u4.fsf@gmail.com> <87wqd1yo84.fsf@Rainer.invalid> <8738fpeyov.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40132) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wr2vX-0001fL-Nj for emacs-orgmode@gnu.org; Sun, 01 Jun 2014 06:23:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Wr2vP-0004ku-T5 for emacs-orgmode@gnu.org; Sun, 01 Jun 2014 06:23:43 -0400 Received: from plane.gmane.org ([80.91.229.3]:55906) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wr2vP-0004kq-MQ for emacs-orgmode@gnu.org; Sun, 01 Jun 2014 06:23:35 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Wr2vN-0003fu-17 for emacs-orgmode@gnu.org; Sun, 01 Jun 2014 12:23:33 +0200 Received: from pd9eb22a0.dip0.t-ipconnect.de ([217.235.34.160]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 01 Jun 2014 12:23:33 +0200 Received: from Stromeko by pd9eb22a0.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 01 Jun 2014 12:23:33 +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: emacs-orgmode@gnu.org Nicolas Goaziou writes: > I didn't like the "wrap" parameter because it mixes parsed blocks (e.g., > wrap quote) and raw blocks (e.g., wrap html). It is important to know if > the parser should parse the contents of the file or not. Therefore, the > new syntax, if any, should make it clear. In the current problem, we > mustn't parse the contents of the file. That's the only problem? Aside from "quote" not being an export backend, I'm afraid I don't really see the difference between #+INCLUDE: "file.ext" src results: and #+INCLUDE: "file.ext" wrap in this case. We can always check if maps to a valid export block and drop back to quoting the whole thing like we do with "src" if not. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds