public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Preserving LaTeX backslash comma
Date: Wed, 29 May 2019 09:25:12 -0700	[thread overview]
Message-ID: <m2woi9mdnb.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <CADAJKhCfSn6t0+M+bv+p6jSixYVe55FVZzgSAO=XoEGdLvmk-A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>


Another approach is to insert a unicode thin space
character in your source document.


      parent reply	other threads:[~2019-05-29 16:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-04 21:43 prevent pandoc from treating paragraph starting with number as list jdh246-Re5JQEeQqe8AvxtiuMwx3w
     [not found] ` <3bf2aa28-2acf-49fc-b155-298ac435d6e6-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-01-04 22:14   ` BP Jonsson
     [not found]     ` <b5ad3894-3c2a-e1b5-0e97-0b5fafc291df-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-01-06  2:58       ` jdh246-Re5JQEeQqe8AvxtiuMwx3w
     [not found]         ` <a8841a5c-d501-4a62-a709-3d6eec8fae8f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-04-15 10:32           ` ~\ref{label} produces \textasciitilde{} Jan David Hauck
     [not found]             ` <CAE4y4Fm-UiTQ8rwJciGQEG=xH_uVO_+o6ZMWmCcyNhqXDor2XQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-04-15 13:09               ` jeremy theler
2019-04-25 14:35   ` prevent pandoc from treating paragraph starting with number as list CR
2019-05-29 13:50   ` Preserving LaTeX backslash comma Jan David Hauck
     [not found]     ` <CAE4y4F=ydNh5aOWyMYbLcWtbCepB6bO67V3Q5ucAd+pS2CwT4w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-05-29 15:13       ` BPJ
     [not found]         ` <CADAJKhCfSn6t0+M+bv+p6jSixYVe55FVZzgSAO=XoEGdLvmk-A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-05-29 16:25           ` John MacFarlane [this message]

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=m2woi9mdnb.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=melroch-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).