[tex-k] IPC and TeX
jbenet at cs.stanford.edu
Sun Oct 2 19:20:39 CEST 2011
Thanks for the responses! consolidating:
On Friday, September 30, 2011 at 1:47 PM, Tom Rokicki wrote:
> The IPC option (at least the way I wrote it originally) does not save any writes
> to disk at all; it just uses an IPC channel to communicate which pages have
> been written to the DVI file already.
> For what you're doing, have you considered simply using a ram disk?
> -- http://cube20.org/ -- http://golly.sf.net/ --
Thanks Tom!Yeah, ram disk, or named pipes, could speed up the process considerably. But I'm also trying to avoid process creation, as it is pretty expensive. There doesn't seem to be any docs out there on how -ipc works. Any specific sources to look at? I'm not familiar with pascal, so i don't follow the code easily.
On Friday, September 30, 2011 at 2:00 PM, Norman Gray wrote:
> Juan, hello.
> Depending on precisely what it is you're aiming to do, you might be interested in looking at Jonathan Fine's 'TeX Daemon'. The last reference I can find to it is from 2001 <http://www.ntg.nl/eurotex/fine.pdf>, but ... no, correction: Jonathan's put the code on bitbucket <https://bitbucket.org/jfine/texlike-daemon>.
> Best wishes,
> Norman Gray : http://nxg.me.uk
Thanks Norman! I tried to get it to work, but didn't. The tex binary just produced empty dvi files. I went through the setup process twice with the same result. I must've missed something. Though jfine's approach seems to be using pipes (py/tex), so that's encouraging!
On Friday, September 30, 2011 at 2:18 PM, Karl Berry wrote:
> Just a hunch, but I suspect you could get considerably further with
> luatex than anything else.
Thanks, Karl! It seems that luatex's main purpose is to enable macros to be written in lua. Is there something about luatex's process that works differently? I see luasocket in the sources. Perhaps there's a way to script it through the callbacks? The docs aren't very descriptive on how. I'll keep exploring the code.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the tex-k