From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Markdown to PDF Bibliography Tweaking Tufte-Handout
Date: Tue, 13 Jun 2023 21:16:20 -0400 [thread overview]
Message-ID: <D2A01A50-396B-4916-8807-81FEAAE84117@gmail.com> (raw)
In-Reply-To: <5d480421-9668-46cf-82c8-3d671dabd9e2n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Use raw attribute:
```{=latex}
\begin{fullwidth}
```
# References
```{=latex}
\end{fullwidth}
```
> On Jun 13, 2023, at 12:20 PM, Chris Blake-Turner <chrisblaketurner-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> (Apologies if this has been answered, but I couldn't find it with some searching.)
>
> I'm using pandoc to convert Markdown to PDF. I'm using --citeproc and a YAML metadata block that specifies the bibliography, with a final "# References". Everything comes out nicely.
>
> The trick is that I'm using the tufte-handout class for LaTeX and would like the make the Bibliography fullwidth. So I'd like something like:
>
> \begin{fullwidth}
> # References
> \end{fullwidth}
>
> Since "#" is special in LaTeX, that gets me a "You can't use `macro parameter character #' in vertical mode" error message.
>
> So the next thing I tried is escaping the hash:
>
> \begin{fullwidth}
> \# References
> \end{fullwidth}
>
> But then that prints "# References".
>
> I'm sure the fix is simple with some YAML etc. know-how that I lack, so thanks in advance for any suggestions!
>
> Chris
>
> --
> 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/5d480421-9668-46cf-82c8-3d671dabd9e2n%40googlegroups.com.
next prev parent reply other threads:[~2023-06-14 1:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 16:20 Chris Blake-Turner
[not found] ` <5d480421-9668-46cf-82c8-3d671dabd9e2n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-06-14 1:16 ` John MacFarlane [this message]
[not found] ` <D2A01A50-396B-4916-8807-81FEAAE84117-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-06-14 11:31 ` chrisblaketurner-Re5JQEeQqe8AvxtiuMwx3w
2023-06-20 15:06 ` Chris Blake-Turner
[not found] ` <C7C74FF6-88B4-4D13-AEEF-7BC25E44CAC7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-06-20 15:20 ` Bastien DUMONT
2023-06-21 20:06 ` Chris Blake-Turner
[not found] ` <A196B74F-79D9-48A4-A368-525F0FF7CF2B-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-06-21 20:19 ` Bastien DUMONT
2023-06-21 20:21 ` Chris Blake-Turner
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=D2A01A50-396B-4916-8807-81FEAAE84117@gmail.com \
--to=fiddlosopher-re5jqeeqqe8avxtiumwx3w@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).