public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Steve Petersen <spetey-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: pdf preparecolorset error (from "linkcolor" YAML option?)
Date: Mon, 7 Jun 2021 11:01:11 -0700 (PDT)	[thread overview]
Message-ID: <06f458e4-88ef-4f4f-a9fa-097288944ebbn@googlegroups.com> (raw)


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

Hello again marvelous pandoc people,

I recently upgraded to 2.14.0.1, and it seems like my 'linkcolor=blue' 
option in YAML no longer works for pdfs from markdown. I get this error:

~~~
Error producing PDF.
! Undefined control sequence.
l.32 \preparecolorset
~~~

I've reproduced this on Mac and linux (both 2.14.0.1). I'm afraid I'm 
ignorant enough of the details to have no idea how to fix this - any ideas? 
MWE attached.

thanks,
Steve

-- 
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/06f458e4-88ef-4f4f-a9fa-097288944ebbn%40googlegroups.com.

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

[-- Attachment #2: link-color-test.text --]
[-- Type: text/plain, Size: 171 bytes --]

---
title: Link colors
author: Steve Petersen
date: 'Last revised: <2021-06-07 13:59:27>'
linkcolor: blue
---

Check out [my website](https://stevepetersen.net) for more.

             reply	other threads:[~2021-06-07 18:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 18:01 Steve Petersen [this message]
     [not found] ` <06f458e4-88ef-4f4f-a9fa-097288944ebbn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-06-07 20:03   ` Bastien DUMONT
2021-06-07 20:14     ` Steve Petersen
     [not found]       ` <CAGk0Nk9TF8fZes_iF==dVj-xQfF5KFntCNysH45D8TXxRow=9g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-06-07 20:52         ` Bastien DUMONT
2021-06-07 21:02         ` Bastien DUMONT
2021-06-07 21:17           ` Steve Petersen
     [not found]             ` <CAGk0Nk9XvnBycy7z63jGNebeHnm0D-4m=c=qPGLj0rx33ViPow-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-06-07 21:57               ` Bastien DUMONT
2021-06-07 22:28                 ` Steve Petersen
     [not found]                   ` <CAGk0Nk9-850ZqJzHrxW6T2m_1th7pBkUJMJhK=xYqXianeXEcA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-06-07 22:48                     ` Bastien DUMONT
2021-06-08  2:10                       ` Steve Petersen

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=06f458e4-88ef-4f4f-a9fa-097288944ebbn@googlegroups.com \
    --to=spetey-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).