public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "'SBJ' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Markdown to LaTeX: unwanted newlines around LaTeX environment
Date: Wed, 4 Oct 2017 05:35:03 -0700 (PDT)	[thread overview]
Message-ID: <bdbfaa4e-8889-4eec-9831-9901eb39e20f@googlegroups.com> (raw)
In-Reply-To: <20171003204332.GA14228@protagoras>


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

Many thanks!

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. Note 
also: inserting an extra newline before and after in the Markdown source 
would result in *two* extra linebreaks before and after, i.e. the old 
(undesired) behaviour.

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

Testing environment \begin{align}
    i^2&=-1\\
    x &= 0
\end{align} for whitespace.


On Tuesday, 3 October 2017 22:43:32 UTC+2, John MacFarlane wrote:
>
> The dev version of pandoc will not give you a blank line 
> in this case -- it knows that equation environments can 
> occur inline. 
>

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/bdbfaa4e-8889-4eec-9831-9901eb39e20f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

  reply	other threads:[~2017-10-04 12:35 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 [this message]
     [not found]       ` <bdbfaa4e-8889-4eec-9831-9901eb39e20f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-04 17:24         ` John MACFARLANE

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=bdbfaa4e-8889-4eec-9831-9901eb39e20f@googlegroups.com \
    --to=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).