Hello,
Omid omidl...@gmail.com writes:
Apologies for waking up this old thread. But is this feature, for
which Achim proposed a patch early on, going to be included in the Org
mode? As of Org-mode version 8.2.7c (8.2.7c-71-g60418c-elpa)
#+INCLUDE: myfile.html html
still does not do a
Omid writes:
In any case, could you (Achim Gratz) please share with us the final
patch that you and Nicolas Goaziou agreed upon?
That is commit 4ed554196b on master.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
SD adaptation for Waldorf rackAttack
Hello,
Apologies for waking up this old thread. But is this feature, for
which Achim proposed a patch early on, going to be included in the Org
mode? As of Org-mode version 8.2.7c (8.2.7c-71-g60418c-elpa)
#+INCLUDE: myfile.html html
still does not do a literal include.
The last discussion I
Nicolas Goaziou writes:
On second thought, we shouldn't bother too much about it, let the user
provide any keyword, and turn it into a block of the same name.
So, for example, both
#+include: file.html html
and
#+include: file.html center
are valid, even though the second one makes
Hello,
Achim Gratz strom...@nexgo.de writes:
Here's the patch for this:
Thank you. Some comments follow.
+If markup is requested, the included content will be placed within an
+appropriate block@footnote{While you can request paragraphs (@samp{verse},
+@samp{quote}, @samp{center}), there
Hello,
Achim Gratz strom...@nexgo.de writes:
I'm not wedded to the name, maybe export has a nicer ring to it (but
that#s also been used differently in Babel, just like almost anything
else you#d be able to come up with).
True.
What I'm talking about is the list of blocks that never can be
Omid omidl...@gmail.com writes:
Hello Nick,
Thanks for your reply. But no, src html results in the included HTML
being processed by Org and wrapped in pre class=src src-html, just
like if the contents of myfile.html were put in
#+BEGIN_SRC html
#+END_SRC
Yes, I misunderstood the doc.
--
Omid writes:
I am trying to include an HTML file (say myfile.html, which has only
the body) in an Org file so that upon export the contents of
myfile.html are /literally/ inserted in the appropriate section of the
exported HTML file.
That's not yet possible. The following patch would
Hello,
Achim Gratz strom...@nexgo.de 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
Nicolas Goaziou writes:
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.
Achim Gratz strom...@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,
Thank you for the patch, Achim.
On 06/01/2014 05:26 AM, Achim Gratz wrote:
Nicolas Goaziou writes:
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
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
Hello,
Omid omidl...@gmail.com writes:
I think #+INCLUDE: should be just that: Include whatever the user is
asking to. No header arguments dumps the file in Org (as it does now),
subject to the usual processing, and a header argument like html wraps
it in the appropriate delimiter, subject
Achim Gratz strom...@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
Nicolas Goaziou writes:
As explained in this thread, it is not necessary to support:
#+INCLUDE: file.ext wrap center
I'm still not getting your argument or I misunderstand what you're
trying to say. Using wrap should produce an export block and nothing
else. So as long as there can be no
Achim Gratz strom...@nexgo.de writes:
I'm still not getting your argument or I misunderstand what you're
trying to say. Using wrap should produce an export block and nothing
else. So as long as there can be no export block named center, the
INCLUDE above would simply raise a user-error
Nicolas Goaziou writes:
However, note that wrap is confusing because it sounds like Babel's
keyword and yet does something different.
I'm not wedded to the name, maybe export has a nicer ring to it (but
that#s also been used differently in Babel, just like almost anything
else you#d be able to
Hello,
I am trying to include an HTML file (say myfile.html, which has only
the body) in an Org file so that upon export the contents of
myfile.html are /literally/ inserted in the appropriate section of the
exported HTML file. Following
http://orgmode.org/manual/Include-files.html, I used
Omid omidl...@gmail.com writes:
Hello,
I am trying to include an HTML file (say myfile.html, which has only
the body) in an Org file so that upon export the contents of
myfile.html are /literally/ inserted in the appropriate section of the
exported HTML file. Following
Hello Nick,
Thanks for your reply. But no, src html results in the included HTML
being processed by Org and wrapped in pre class=src src-html, just
like if the contents of myfile.html were put in
#+BEGIN_SRC html
#+END_SRC
Omid
Sent from my Emacs
On 06/01/2014 12:42 AM, Nick Dokos wrote:
Here is a minimal example, in case someone wants to try
myfile.html:
p
bHello, World!/b
/p
orgincludehtml.org:
* Test
#+INCLUDE: ./myfile.html html
I am using Org-mode version 8.2.6 (from ELPA) and GNU Emacs 24.3.1.
Omid
Sent from my Emacs
On 06/01/2014 12:42 AM, Nick Dokos wrote:
Omid
22 matches
Mail list logo
