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 12:01:04 +0200 [thread overview]
Message-ID: <8738fpeyov.fsf@gmail.com> (raw)
In-Reply-To: <87wqd1yo84.fsf@Rainer.invalid> (Achim Gratz's message of "Sun, 01 Jun 2014 11:26:51 +0200")
Achim Gratz <Stromeko@nexgo.de> writes:
> Nicolas Goaziou writes:
>> 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.
>
> Please not.
Why?
>> 2. Extend "src" syntax to allow Babel parameters after the language.
>> E.g.,
>>
>> #+INCLUDE: "file.html" src html :results html
>
> That looks better, but still isn't quite self-explanatory. What
> happens if I write
>
> #+INCLUDE: "file.html" src html :results elisp
>
> for instance?
The same as if you write
#+INCLUDE: "file.html" src html
but with an additional :results elisp Babel parameter, whatever it may
mean.
> That would still wrap the include file with an almost arbitrary block,
> no?
> I don't think you can check that the file to be included fulfills
> all the requirements of being included at that point anyway.
We don't need to.
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.
> Here are two more options with different degrees of iffyness:
>
> #+INCLUDE_HTML: "file.html"
This would extend Org syntax, by a large part. This is not necessary for
the problem at hand.
> #+BEGIN_HTML
> <<"file.html">>
> #+END_HTML
Again, I don't want to extend Org syntax, or only by a tiny part, hence
the two proposals above.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-06-01 10:00 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 [this message]
2014-06-01 10:23 ` Achim Gratz
2014-06-01 11:30 ` Nicolas Goaziou
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=8738fpeyov.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).