public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: gnpan <g.panayotou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Problem with colored urls or links
Date: Fri, 12 Aug 2022 11:44:06 -0700 (PDT)	[thread overview]
Message-ID: <589c27c9-ccf6-4693-8f14-98b59a61047fn@googlegroups.com> (raw)


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

I used to be able to get colored urls just by adding urlcolor: red in the 
YAML header or -V urlcolor=red in the command. This no longer seems to work 
in 2.19, unless I use older templates. I tried loading hyperref under 
header-includes and other tricks suggested at various places, but no luck. 

So the following example (file test.md):

```
---
urlcolor: red
---

[A url](https:www.google.com)

```
with the command:

```
pandoc --pdf-engine=xelatex -o test.pdf test.md

```

or with no YAML and 

```
pandoc --pdf-engine=xelatex —V urlcolor=red -o test.pdf test.md

```

gives a black url rather than red. 

Any help appreciated. 

-- 
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/589c27c9-ccf6-4693-8f14-98b59a61047fn%40googlegroups.com.

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

             reply	other threads:[~2022-08-12 18:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-12 18:44 gnpan [this message]
     [not found] ` <589c27c9-ccf6-4693-8f14-98b59a61047fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-08-13  7:40   ` Albert Krewinkel
     [not found]     ` <874jygpoz9.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-08-13  8:40       ` gnpan

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=589c27c9-ccf6-4693-8f14-98b59a61047fn@googlegroups.com \
    --to=g.panayotou-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).