Make failed. Undefined control sequence (\passthrough)

[wizofe]

System Information:

MAC OSx High Sierra 10.13.2
Darwin UNKNOWN 17.3.0 Darwin Kernel Version 17.3.0; root:xnu-4570.31.3~1/RELEASE_X86_64 x86_64
pandoc version 2.1.1
pdfTeX 3.14159265-2.6-1.40.18 (TeX Live 2017)
XeTeX 3.14159265-2.6-0.99998 (TeX Live 2017)

Changed the Makefile parameters to be compatible with pandoc 2.1.1 as follows:

--pdf-engine $(XELATEX)
--top-level-division=chapter -N --toc --toc-depth=2 \

After running make though I am getting:

fatal: your current branch 'master' does not have any commits yet
> Error producing PDF.
! Undefined control sequence.
<recently read> \passthrough

l.7517   \passthrough

make: *** [pdf] Error 43

[timparenti]

Hi, @wizofe. Could you post your full updated Makefile recipe for the pdf target, and not just a couple lines? On first glance, it seems like the line continuation \ at the end of your --pdf-engine line is missing.

As for the fatal: your current branch 'master' does not have any commits yet error, how are you cloning the repository?

[wizofe]

Hi @timparenti! Thanks for your answer ⌨️My Makefile paste follows. As for the git fatal, I git forked & cloned the repo on my account.

TITLE=A Friendly Introduction\\\\to Software Testing
AUTHOR=Bill Laboon
DEDICATION=for AKS and CKN


# If pandoc or xelatex are not in your PATH, specify their locations here:
PANDOC= pandoc
XELATEX= xelatex

MD_FILES=       $(wildcard text/*.md)


pdf:    main.tex tex_files
# Uses date of most recent commit in repo
        $(PANDOC) main.tex -o software-testing-laboon-ebook.pdf \
                --pdf-engine $(XELATEX) \
                --top-level-division=chapter -N --toc --toc-depth=2 \
                -M documentclass="book" \
                -M classoption="twoside" \
                -M classoption="letterpaper" \
                -M geometry="margin=1.25in" \
                -M title="\Huge{\textbf{${TITLE}}}" \
                -M author="\LARGE{${AUTHOR}}" \
                -M date="{\Large\textcopyright~\textbf{$(shell git log -1 --date=iso --format='%ai' | cut -c-10 )}}\\\\Compiled in PDF\LaTeX{}\endgraf\textit{${DEDICATION}}"

tex_files:      compiled_tex/ $(patsubst text/%.md,compiled_tex/%.tex,$(MD_FILES))
compiled_tex/:
        mkdir -p compiled_tex/
compiled_tex/%.tex:     text/%.md
        $(PANDOC) text/$*.md \
                --listings --highlight-style kate \
                -o compiled_tex/$*.tex


clean:
        rm -rf compiled_tex/
        # Remove temporary compilation directories, if they still exist
        rm -rf tex2pdf*/

.PHONY: pdf tex_files clean

[yonush]

Hi @wizofe. I was getting the same issue under windows. I am using Pandoc 2.1.1 and MiKTeK 2.9.6520 x64 with a custom build script - essentially batch file that creates the PDF and epub

I managed to trace my problem to this file - lines 670-672

41_advanced_unit_testing.md

For some odd reason the emitted latex code does not parse very well and i'm not an expert in latex commands. I changed it to the following, which is probably not the best solution, but it generates the PDF without issues.

[timparenti]

@yonush Any chance you'd be able to provide the (bad) LaTeX code that pandoc generates for those lines as they appear in this repo? It's possible it's a bug in the upstream project, which has happened here before.

[yonush]

@timparenti This appears to be the bad code generated by Pandoc that breaks.
This is the excerpt from the input.log

[timparenti]

Yep, with Pandoc 2.1.1, I get the following in compiled_tex/41_advanced_unit_testing.tex at lines 1106–1115:

\begin{enumerate}
\def\labelenumi{\arabic{enumi}.}
\tightlist
\item
  \passthrough{\lstinline!int j = 7;!}
\item
  \passthrough{\lstinline&System.out.println("Bark!");&}
\item
  \passthrough{\lstinline!foo--;!}
\end{enumerate}

I finally got around to looking at this more, and greping through the compiled_tex/ files, I see most \lstinlines use a ! delimiter, but those with ! in them use ". It seems & is the third choice if both ! and " are used, and the "Bark!" line here is the only place that happens in our text.

Ampersands are funny creatures in LaTeX. They generally need to be escaped when you want them to be treated as literal. It seems that something about the dummy \passthrough command Pandoc introduced recently to help with escaping is not actually expecting these ampersands.

Probably & should just be removed from the list of characters that can delimit a \lstinline in Pandoc's LaTeX writer, since it requires special treatment, which was recognized in jgm/pandoc@24acb71 just before 2.1.1 was released. Interestingly, _ should probably meet the same fate, but it's less likely to crop up as an issue since it's currently the sixteenth-choice delimiter.

I've just opened jgm/pandoc#4369 against the upstream project to do this. Thanks for reporting this behavior!

[TiburonzinGT]

@timparenti Hello, I would like to translate to Spanish but I do not know how. I would like to do it by means of pull request :)

[laboon]

@shadowz10 I would love to see this translated into Spanish! It may make more sense to do this a separate repository, though, instead of as a PR.

[TiburonzinGT]

@laboon I do translations for utopian.io and they require that it be with PR.
I would love to contribute with translations into Spanish by doing PR.

[TiburonzinGT]

@laboon If you want, I could set up a repository so I can work making a
PR. thanks

[timparenti]

@laboon @wizofe Just a note that jgm/pandoc#4369 was merged upstream on 26 April 2018 and released in pandoc 2.2 on 27 April 2018.

I just re-ran this with a fresh upgrade to pandoc 2.2.1 via Homebrew (with the updated Makefile parameters for pandoc 2.x in #144), and it now compiles cleanly, so this one can probably be closed now.

[laboon]

@wizofe if this works for you, let me know and I can close it up.