public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Lyndon Drake <lyndon-S8RYeTzMgQ3QT0dZR+AlfA@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Possible bug with defaults and raw latex in header
Date: Mon, 20 Apr 2020 13:51:29 -0700 (PDT)	[thread overview]
Message-ID: <28a7dbf5-113c-4287-be57-96996e083406@googlegroups.com> (raw)
In-Reply-To: <m2lfmqp1a0.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 2076 bytes --]

For clarity, this is what ends up in the LaTeX file:

\textbackslash usepackage\{imakeidx\}

Is there a way to include raw LaTeX in the defaults file, and avoid having 
it escaped (the \textbackslash etc. in there)?

What's the best way to include raw LaTeX using a defaults file?

Best,
Lyndon

On Tuesday, 21 April 2020 04:31:19 UTC+12, John MacFarlane wrote:
>
>
> Yes, this is intended. In a markdown file YAML fields are parsed 
> as Markdown.  So if you want raw LaTeX you need to indicate this 
> as you do.  In a defaults file metadata section, it works just 
> like with --metadata-file or --metadata on the command line: 
> the contents are interpreted as plain strings. 
>
> Lyndon Drake <lyn...-S8RYeTzMgQ3QT0dZR+AlfA@public.gmane.org <javascript:>> writes: 
>
> > Hi, 
> > 
> > When I put the following in a YAML block in my Markdown file: 
> > 
> >   header-includes: 
> >   - | 
> >     ```{=latex} 
> >     \usepackage{imakeidx} 
> >     ``` 
> > 
> > it works fine. The same text in a defaults file, in the metadata: 
> section, 
> > ends up in the LaTeX file after being backslash-escaped. 
> > 
> > Is that intended behaviour? If not I'll put a bug report in the issue 
> > tracker. 
> > 
> > Best, 
> > Lyndon 
> > 
> > -- 
> > 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-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>. 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/pandoc-discuss/bd07e9d0-e3f8-481b-9a3f-3c952b11499c%40googlegroups.com. 
>
>

-- 
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/28a7dbf5-113c-4287-be57-96996e083406%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 3633 bytes --]

  parent reply	other threads:[~2020-04-20 20:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20  8:17 Lyndon Drake
     [not found] ` <bd07e9d0-e3f8-481b-9a3f-3c952b11499c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-04-20 16:31   ` John MacFarlane
     [not found]     ` <m2lfmqp1a0.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-04-20 20:51       ` Lyndon Drake [this message]
     [not found]         ` <28a7dbf5-113c-4287-be57-96996e083406-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-04-20 21:21           ` John MacFarlane

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=28a7dbf5-113c-4287-be57-96996e083406@googlegroups.com \
    --to=lyndon-s8ryetzmgq3qt0dzr+alfa@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).