From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: #+INCLUDE: myfile.html html does not include /literally/; Org processes
Date: Sun, 01 Jun 2014 13:30:33 +0200 [thread overview]
Message-ID: <87r438eujq.fsf@gmail.com> (raw)
In-Reply-To: <87sinpylly.fsf@Rainer.invalid> (Achim Gratz's message of "Sun, 01 Jun 2014 12:23:21 +0200")
Achim Gratz <Stromeko@nexgo.de> writes:
> 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 <lang> results: <lang>
>
> and
>
> #+INCLUDE: "file.ext" wrap <lang>
As explained in this thread, it is not necessary to support:
#+INCLUDE: "file.ext" wrap center
> in this case. We can always check if <lang> maps to a valid export
> block and drop back to quoting the whole thing like we do with "src" if
> not.
The "check" part is useless if we assume that any "wrap", "export",
"raw" or whatever parameter implies that the contents of the file are
specific to an export back-end.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-06-01 11:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-01 4:06 #+INCLUDE: myfile.html html does not include /literally/; Org processes Omid
2014-06-01 4:42 ` Nick Dokos
2014-06-01 4:51 ` Omid
2014-06-01 6:18 ` Nick Dokos
2014-06-01 5:05 ` Omid
2014-06-01 7:53 ` Achim Gratz
2014-06-01 8:31 ` Nicolas Goaziou
2014-06-01 9:26 ` Achim Gratz
2014-06-01 10:01 ` Nicolas Goaziou
2014-06-01 10:23 ` Achim Gratz
2014-06-01 11:30 ` Nicolas Goaziou [this message]
2014-06-01 13:02 ` Achim Gratz
2014-06-01 14:00 ` Nicolas Goaziou
2014-06-01 14:27 ` Achim Gratz
2014-06-03 20:37 ` Nicolas Goaziou
2014-06-04 21:50 ` Achim Gratz
2014-06-05 9:28 ` Nicolas Goaziou
2014-06-07 10:11 ` Achim Gratz
2014-06-07 13:53 ` Nicolas Goaziou
2014-06-01 10:01 ` Omid
2014-06-01 11:24 ` Nicolas Goaziou
-- strict thread matches above, loose matches on Subject: below --
2014-09-25 22:36 Omid
2014-09-26 9:07 ` Nicolas Goaziou
2014-09-26 18:53 ` Achim Gratz
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=87r438eujq.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=Stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.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).