raw tex not filtered if it includes \begin or \end

[zeeMonkeez]

---
title: test
header-includes:
- \newcommand{\benv}{\begin{env}}
- \newcommand{\eenv}{\end{env}}
- \newcommand{\tenv}{test}
---

\benv
env1
\eenv

\begin{env}
env2
\end{env}

\tenv

Calling pandoc rt.md -o rt.html produces:

<p>\benv env1 \eenv</p>

Expected output:

<p>env1</p>

I would not expect the command definition of \benv and \eenvto be parsed, as that would be nontrivial, to produce output consistent with the \begin{env}…\end{env}. Instead, I would expect output consistent with behaviour from \tenv.

pandoc compiled from ea1724e.

[jgm]

So the issue is that, when a macro for `\benv` is defined in the document, it gets parsed as a plain string. When no macro is defined, things work as expected. I'll have to look into this. I suspect the problem is that `\benv` expands into something that can't be parsed either as an inline or as a block element (since it's just part of a block). The real issue is that pandoc tries to resolve the macros piecemeal, instead of resolving them and changing the input stream. See #982. In fact, I think this can probably be closed as a dup of #982.