\newcommand in a document header is totally different to a \newcommand in the defaults header

\newcommand in a document header is totally different to a \newcommand in the defaults header

[Oliver]

[-- Attachment #1: Type: text/plain, Size: 944 bytes --]

In a defaults file I have e.g:

```
variables:
   header-includes:
     - \newcommand{\mydef}{My definition}
```

This will provide for the TeX document the command `\mydef`.

In my Markdown document I have

```
---
header-includes:
   - \newcommand{\yourprop}{Your proposition}

...

This will *not* provide  a command `\yourprop`, instead every time when 
in the source `\yourprop` appear it will be replaced *by pandoc* with 
„Your proposition“.

Where on earth is this behaviour coming from?

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/2AFD24A5-E14B-4348-9520-F233E1854E26%40halloleo.hailmail.net.

[-- Attachment #2: Type: text/html, Size: 2019 bytes --]