Re: pdfroff invalid argument on cygwin

["jlr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <jlrn77-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]

[-- Attachment #1.1: Type: text/plain, Size: 1758 bytes --]



Il giorno mercoledì 25 novembre 2020 alle 20:30:44 UTC-6 John MacFarlane ha 
scritto:

>
> > After a bit of research, it seems that indeed the problem is the call to 
> > the system to process pandoc's output through stdin: windoze is infamous 
> > for that; since the other processors go through temporary files, the 
> output 
> > call proceeds flawlessly, as the cmd shell has an input file to find. 
> > 
> > So perhaps the only solution, not the workaround, is to ask pdfroff to 
> > process a tmp file generated by pandoc, as other pdf-engines do. Not as 
> > elegant as calling the pipe, but probably more portable. 
>
> Makes sense probably. If you submit an issue on the GitHub 
> tracker, we'll be less likely to lose track. 
>
> (Of course, Windows is also a bit of a pain when it comes to tmp 
> files, but what we're doing for the other methods seems to work.)


Hello!

In the process of cleaning up my memories (the usbs and other devices) I 
recalled this utility, shc (shell compiler), which produces an exe based on 
a shell script. I compiled a pdfroff.exe based on the bash pdfroff bundled 
with cygwin, and the process goes on flawlessly.

I don't know if I should still open the issue, or post this discussion 
somewhere else on the net, like stackexchange or something...

Curious,

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/60aaaf2c-fa98-422a-a0a5-b998e56ebf55n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 2389 bytes --]