public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: backslash-escaped leading space in markdown table treated as a literal backslash
Date: Wed, 7 Feb 2018 08:52:57 -0800	[thread overview]
Message-ID: <20180207165257.GH88252@Johns-MacBook-Pro.local> (raw)
In-Reply-To: <1f5e2447-795b-45d4-991b-ed5a55ea706c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

+++ John Muccigrosso [Feb 05 18 12:32 ]:
>   I think this is a relatively recent regression. `\ ` at the start of a
>   line normally gets treated as a space:
>   > pandoc
>   one
>   \ two
>   three
>   <p>one</p>
>   <p> two</p>
>   <p>three</p>
>   But if it's in a table, it gets preserved now. HTML below:
>   > pandoc
>   one | one
>   ----|---
>   two | two
>   \   | three

This is because we strip trailing spaces before parsing the
cell (that's not a new change).  Note that if you have
`\ a` in your cell, the escaped space will work; it's only
at the end that it doesn't, and this mirrors how a paragraph
ending in a `\` with no following space is treated.

Are there real-world examples where you need the `\ ` in a
cell with nothing else?


  parent reply	other threads:[~2018-02-07 16:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-05 20:32 John Muccigrosso
     [not found] ` <1f5e2447-795b-45d4-991b-ed5a55ea706c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-02-07 16:52   ` John MacFarlane [this message]
     [not found]     ` <20180207165257.GH88252-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2018-02-07 21:37       ` John Muccigrosso
     [not found]         ` <f1c851a4-d1fd-4d2e-a881-d7ad76eb05d6-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-02-09 23:26           ` John Muccigrosso

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=20180207165257.GH88252@Johns-MacBook-Pro.local \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@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).