public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MACFARLANE <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: 'SBJ' via pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Markdown to LaTeX: unwanted newlines around LaTeX environment
Date: Wed, 4 Oct 2017 10:24:23 -0700	[thread overview]
Message-ID: <20171004172423.GE20306@protagoras> (raw)
In-Reply-To: <bdbfaa4e-8889-4eec-9831-9901eb39e20f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

+++ 'SBJ' via pandoc-discuss [Oct 04 17 05:35 ]:
>   I can confirm that Pandoc 2.0 (dev) renders this without the additional
>   newlines, as shown below. Note, however, that there are now two
>   linebreaks fewer before and after the environment, respectively
>   (compared to the old output), so that the entire environment is now
>   inlined with the rest of the LaTeX source. pdflatex does not seem to
>   take issue with this and renders it correctly, but I wanted to point it
>   out nevertheless.

Yes, I'm aware of this, but it's not a problem; the latex is valid.

>   Also, thank you for developing Pandoc. Besides being conceptually
>   interesting, I find it incredibly useful for my day-to-day work.

You're welcome!


      parent reply	other threads:[~2017-10-04 17:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-03 16:51 'SBJ' via pandoc-discuss
     [not found] ` <8729b9a5-1aff-4d3a-a17f-06d8a63beefa-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-03 20:43   ` John MACFARLANE
2017-10-04 12:35     ` 'SBJ' via pandoc-discuss
     [not found]       ` <bdbfaa4e-8889-4eec-9831-9901eb39e20f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-04 17:24         ` 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=20171004172423.GE20306@protagoras \
    --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).