Pandoc issue when \include is the first thing in a lilypond environment

[uliska]

When the first element in a \begin{lilypond} environment is \include Pandoc scrambles the output by escaping everything, making the thing fail miserably.

This is a Pandoc parsing problem, and I've opened an issue there, this one here is just for reference.

[fedelibre]

@uliska The issue you mentioned eventually was solved: lilypond and ly environments will be treated as a verbatim environment starting from Pandoc 2.2.2.

I'm having this problem with Pandoc 2.1.2. I look forward to updating.

[fedelibre]

Pandoc update in Fedora is taking some time. I'll see if I can test the .deb file distributed by Pandoc on Github.

[dbitouze]

When the first element in a \begin{lilypond} environment is \include

BTW, I would advise against \include in a lilypond environment. What would be advised for this use case is \input which just, well, input the content of the specified file, while \include first does a \clearpage which, if desired, is better done manually before \begin{lilypond}.

[uliska]

No, \include ist a proper LilyPond command that can"t be forbidden. That"s the source of the issue.

[dbitouze]

OK, sorry for the noise.