Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
pipe from stdin to latex ?
2,348 views
Skip to first unread message
iaw4
Jul 8, 2013, 11:02:08 AM7/8/13
to
I am thinking of trying out multimarkdown as a preprocessor for latex memoir input.
it would be perfect if I could just pipe output from mmd to latex. short of writing first to a file and then \input it (which loses the multicore usefulness), or write to a .tex file and then run it, is there an easy way to induce latex to read its input from stdin?
one issue is that the naming of the input file is used for the file extensions. but this could be read from a comment on the first line (and passed by mmd). if no name is passed, it could be a default name or the epoch time.
5 vs 6 seconds process time is no big deal...but my book takes about 1-2 minutes to process.
Robin Fairbairns
Jul 9, 2013, 7:24:29 AM7/9/13
to
iaw4 <ivo...@gmail.com> writes:
> I am thinking of trying out multimarkdown as a preprocessor for latex
> memoir input.
>
> it would be perfect if I could just pipe output from mmd to latex.
> short of writing first to a file and then \input it (which loses the
> multicore usefulness), or write to a .tex file and then run it, is
> there an easy way to induce latex to read its input from stdin?
i've tried this in the past, and gave up.
> I am thinking of trying out multimarkdown as a preprocessor for latex
> memoir input.
>
> it would be perfect if I could just pipe output from mmd to latex.
> short of writing first to a file and then \input it (which loses the
> multicore usefulness), or write to a .tex file and then run it, is
> there an easy way to induce latex to read its input from stdin?
> one issue is that the naming of the input file is used for the file
> extensions. but this could be read from a comment on the first line
> (and passed by mmd). if no name is passed, it could be a default name
> or the epoch time.
>
> 5 vs 6 seconds process time is no big deal...but my book takes about
> 1-2 minutes to process.
for compilation inside 10 minutes.
in fact, we all get sold[*] multi-core processors, and 99.99% of the
time, only one core is active. how long does your conversion to latex
take, stand-alone? -- you're unlikely to gain even that much time by
having it running in another core.
i don't doubt that your dream is achievable. whether the time saved
justifies the amount of effort expended, is another matter...
sorry ;-)
[*] in my case, the _department_ is sold. the last machine i bought for
myself had a 50mhz processor, and i thought it pretty amazing.
--
Robin Fairbairns, Cambridge
Rolf Niepraschk
Jul 10, 2013, 10:39:31 AM7/10/13
to
iaw4
Jul 11, 2013, 12:57:29 AM7/11/13
to
thx, ralf. no perl?? :-). looks interesting. regards, /iaw
Peter Flynn
Jul 12, 2013, 4:45:07 PM7/12/13
to
On 07/08/2013 04:02 PM, iaw4 wrote:
> is there an easy way to induce latex to read its input from stdin?
It does this by default. Write a small LaTeX document, then type
> is there an easy way to induce latex to read its input from stdin?
cat mydoc.tex | pdflatex -jobname=mydoc
///Peter
0 new messages