Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tikz conflict #184

Open
noraj opened this issue Aug 1, 2020 · 2 comments · May be fixed by #185
Open

tikz conflict #184

noraj opened this issue Aug 1, 2020 · 2 comments · May be fixed by #185

Comments

@noraj
Copy link
Contributor

noraj commented Aug 1, 2020

I have this random error occurring:

Error producing PDF.
! Package tikz Error: Sorry, some package has redefined the meaning of the math
-mode dollar sign. This is incompatible with tikz and its calc library and migh
t cause unrecoverable errors.

See the tikz package documentation for explanation.
Type  H <return>  for immediate help.
 ...                                              
                                                  
l.380 \end{verbatim}

I was not able to find which content exactly was generating the error, it seems to be very contextual.

But I found this workaround: https://tex.stackexchange.com/questions/165929/semiverbatim-with-tikz-in-beamer/165937#165937

\makeatletter
\global\let\tikz@ensure@dollar@catcode=\relax
\makeatother

I just added it here in the template
image

Since tikz is loaded only when titlepage-background is used only people using this option could possibly encounter the error.

noraj added a commit to noraj/pandoc-latex-template that referenced this issue Aug 1, 2020
@noraj noraj linked a pull request Aug 1, 2020 that will close this issue
@maxodoble
Copy link

hi,

this workaround was working o.k. for me too, but today i got this tikz error message again, even though the workaround is still active.

any ideas why this workaround could have stopped working?

@maxodoble
Copy link

hi,

this workaround was working o.k. for me too, but today i got this tikz error message again, even though the workaround is still active.

any ideas why this workaround could have stopped working?

Forget this, made a stupid mistake myself!
the workaround is o.k.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants