public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "R (Chandra) Chandrasekhar" <chyavana-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
	Gwern Branwen <gwern-v26ZT+9V8bxeoWH0uzbU5w@public.gmane.org>
Subject: Re: Colon in title in YAML header block
Date: Wed, 20 Sep 2017 22:21:08 +0530	[thread overview]
Message-ID: <16f23044-d51d-cb0d-fb5e-63f11df2ed5a@gmail.com> (raw)
In-Reply-To: <CAMwO0gy5r5TA_PDEzYZLW7yHU2kYOqPdHWGWHE8oY3ZzAWdnSw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Thank you. Both single and double quotes work.

I do not know YAML well and think that I had been overly fixated on 
backslash escaping to consider alternatives.

Chandra

On 20/09/17 22:11, Gwern Branwen wrote:
> Don't you quote it like any other string literal?
> 
>      ---
>      title: "This title: has a colon"
>      ----
> 
> That's always seemed to fix escaping problems in my Hakyll files' metadata.
> 


  parent reply	other threads:[~2017-09-20 16:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-20 16:35 R (Chandra) Chandrasekhar
     [not found] ` <ffc43c46-a1a5-cb39-b103-cc0a8dddcb19-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-09-20 16:41   ` Gwern Branwen
     [not found]     ` <CAMwO0gy5r5TA_PDEzYZLW7yHU2kYOqPdHWGWHE8oY3ZzAWdnSw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-09-20 16:51       ` R (Chandra) Chandrasekhar [this message]
     [not found]         ` <16f23044-d51d-cb0d-fb5e-63f11df2ed5a-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-09-20 20:13           ` BP Jonsson
     [not found]             ` <CAFC_yuRBc0CvG8hgV0z+HZzwmRcWXjC7KrL1Rtvj1xyY=0-OUw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-09-21  3:44               ` R (Chandra) Chandrasekhar

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=16f23044-d51d-cb0d-fb5e-63f11df2ed5a@gmail.com \
    --to=chyavana-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=gwern-v26ZT+9V8bxeoWH0uzbU5w@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).