Closed jfbu closed 5 years ago
I'm not sure that this is a bug, or if the package can do anything about it, you locally (via \do@noligs
) make '
active, so \my@file
ends up being a macro that holds a single token, a catcode 13 '
. But unlike your commented out "no problem here" case, you evaluate \my@file
in a different scope where the noligs definition is not in force so you get the usual active definition which assumes math mode ^{\prime}
If you locally restore the noligs definition when using the macro it works as expected
\newcommand\myVerbInput[1]
{\CatchFileDef{\my@file}{#1}{\@vobeyspaces\@noligs}{\@noligs\my@file}}
oh yes I had not looked closely. The token is active but not with the definition done by \@noligs
. Obvious in retrospect... feel free to close this. (sorry I did not look at a trace nor did I do any thinking before raising "issue", I had been too busy trimming out things to get to mwe first... )
(sorry for noise... my brain disconnects more and more areas...)
produces
Note: the
\@vobeyspaces
is only there because\do@noligs
is lacking a spaceafter
\char
#1hence normal space may be gobbled. Thus I made the space active (usually in such a "verbatim" like setting but with normal spaces, I modify the
\do@noligs`). But the problem shows the same without it.