On Mon, May 09, 2016 at 04:10:37PM +0000, Grant Edwards wrote: > On 2016-05-09, 'Marco Ciampa' via asciidoc <[email protected]> wrote: > > On Mon, May 09, 2016 at 02:03:06PM +0000, Grant Edwards wrote: > >> On 2016-05-09, 'Marco Ciampa' via asciidoc <[email protected]> > >> wrote: > >> > On Mon, May 09, 2016 at 10:26:27AM +1000, Lex Trotman wrote: > >> >> Where would it be "included"? > >> > > >> > On the top, following the order of arguments like the include directive > >> > in the file. > >> > > >> > Like this: > >> > > >> > asciidoctor --include file1.adoc --include file2.adoc textfile.adoc > >> > >> One way this is done in bash is: > >> > >> $ asciidoctor <(cat file1.adoc file2.adoc textfile.adoc) > > > > Great idea, thanks! > > Perhaps my post wasn't clear.
No, it was clear, it's my fault, I was in a hurry... > That doesn't work for either asciidoc > or asciidoctor because they both fail when the input file is a FIFO > (which is what happens when you used the <(cmd) syntax in bash. > > The other way to do it (which does work); > > $ cat file1.adoc file2.adoc textfile.adoc | asciidoctor - >output.html > > [I had assumed that if asciidoc(tor) couldn't handle a FIFO, it > couldn't handle a pipe either so I didn't even suggest it, but it > looks like it does work.] That is really interesting since I though that a FIFO was a PIPE (an anonymous PIPE) but evidently I was wrong (again)... Anyway that resolve my issue, thanks! -- Marco Ciampa I know a joke about UDP, but you might not get it. ------------------------ GNU/Linux User #78271 FSFE fellow #364 ------------------------ -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
