Enable latex_macros for output writers

[asmaier]

Enable latex_macros for output writers

[jgm]

Note that you can always turn off the raw attribute extension:
-t markdown-raw_attribute.

[jgm]

I've changed the writer so it doesn't use raw_attribute syntax unless there is no other option.

[jgm]

However this won't render correctly.

Can you expand on this? How are you rendering this md document?

So my suggestion would be to not extend latex macros if the output format has explicitily activated the extension latex_macros

The expansion takes place in the reader. By the time the writer gets it, it has already been expanded and there is nothing the writer can do to "unexpand" it. So, this needs to be a reader extension.

[asmaier]

However this won't render correctly.

Can you expand on this? How are you rendering this md document?

I was using

 pandoc --mathjax -s -f markdown -t html5 -o test.html test.md

But this will not work correctly, because the \newcommands will be ignored.

So my suggestion would be to not extend latex macros if the output format has explicitily activated the extension latex_macros

The expansion takes place in the reader. By the time the writer gets it, it has already been expanded and there is nothing the writer can do to "unexpand" it. So, this needs to be a reader extension.

Ok, I understand. I was more thinking about a "readable" command line, ignoring the inner workings of pandoc. I still think it would be nice if the result in the markdown file would look like

    \newcommand{\lra}[1]{ \left( #1 \right) }
    \newcommand{\lrb}[1]{ \left[ #1 \right] }
    \newcommand{\lrc}[1]{ \left\{ #1 \right\} }

instead of

    ```{=latex}
    \newcommand{\lra}[1]{ \left( #1 \right) }
    ```
    ```{=latex}
    \newcommand{\lrb}[1]{ \left[ #1 \right] }
    ```
    ```{=latex}
    \newcommand{\lrc}[1]{ \left\{ #1 \right\} }
    ```

so that the latex macros won't get ignored when rendering the markdown.

[jgm]

so that the latex macros won't get ignored when rendering the markdown.

Right. I guess that's something I hadn't considered in telling the Markdown writer to use the raw attribute syntax. We could (a) in the markdown writer, avoid using the raw attribute syntax, at least for macro definitions, or (b) in the markdown reader, process macros even when in raw blocks.

[asmaier]

From a user perspective I would choose option (a), because it leads to a simpler markdown file.