From: Oliver <news-WPTjrydoUPgeaOpM6FAJmQkbCANdLtlA@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: \newcommand in a document header is totally different to a \newcommand in the defaults header
Date: Thu, 25 May 2023 21:46:40 +1000 [thread overview]
Message-ID: <2AFD24A5-E14B-4348-9520-F233E1854E26@halloleo.hailmail.net> (raw)
[-- 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 --]
reply other threads:[~2023-05-25 11:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2AFD24A5-E14B-4348-9520-F233E1854E26@halloleo.hailmail.net \
--to=news-wptjrydoupgeaopm6fajmqkbcandltla@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).