Re: pdfroff invalid argument on cygwin

[John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>]

"jlr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <jlrn77-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> --verbose reports, on -t ms
>
> [makePDF] Command line:
> pdfroff "-ms" "-mpdfmark" "-mspdf" "-e" "-t" "-k" "-KUTF-8" "-i"
>
> while on -t latex
>
> [makePDF] Command line:
> pdflatex "-halt-on-error" "-interaction" "nonstopmode" "-output-directory" 
> "./tex2pdf.-573d55defdd5e31a" "./tex2pdf.-573d55defdd5e31a/input.tex"
>
> So somehow the command line seems to be incomplete for the -ms option: it 
> does not point to the input source.

It's functioning as a pipe in this case; pandoc sends the text
of the source file to stdin in the process.

These options are exactly what I see, and it works fine for me.
So I'm at a loss.

Do you get any informative error message?

What pdfroff version?

Does it fail for any input (even a simple "hello world") or
does the failure depend on some specific feature of the input?

Can you try creating an .ms file using 'pandoc -t ms -s' and
compiling it manually with pdfroff?  Maybe your pdfroff setup
is not right.

> Moreover: I can't see the difference between pandoc.discuss and the bug 
> tracker system on github. Any policy on this subject?

pandoc-discuss is for questions and open-ended discussion,
the tracker is for more focused bug reports.  This type of
thing could go either place; if you think it might not be a bug but
user error or an issue with your setup, going to pandoc-discuss
first is best.