public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: In-paragraph code between backticks and spaces
Date: Mon, 14 Oct 2013 07:21:09 -0700	[thread overview]
Message-ID: <20131014142109.GA9935@Johns-MacBook-Pro.local> (raw)
In-Reply-To: <CAKw7uVgJABVunxbkUKMZf0z=n8z41TsuEbKGohuNNkHdLS8kmg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

+++ Václav Zeman [Oct 14 13 16:08 ]:
> Hi.
> 
> I am seeing extra spaces in output when the text between backticks
> spans multiple lines. E.g., the following text is wrapped (by Emacs)
> inside the backticks block:
> 
> - To configure Digest authentication, use the following lines. Put
>   them below other `auth_param` blocks but before `acl password
>   proxy_auth REQUIRED`.
> 
> The result (DOCX and HTML at least) then contains three spaces between
> "password" and "proxy_auth". Is there a way to let Pandoc contract 3
> spaces into one?

No, nor would this be desirable.  It's important to preserve the ability
to put multiple consecutive spaces in a code span.

IN your example, the spaces are clearly indentation.  But since markdown
doesn't require the list content to be indented, it's hard for the
program to tell.

Best approach would be to set up emacs so that it doesn't break code
spans when wrapping.  (Maybe something for pandoc-mode if it doesn't
already work this way?)

-- 
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/20131014142109.GA9935%40Johns-MacBook-Pro.local.
For more options, visit https://groups.google.com/groups/opt_out.


  parent reply	other threads:[~2013-10-14 14:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-14 14:08 Václav Zeman
     [not found] ` <CAKw7uVgJABVunxbkUKMZf0z=n8z41TsuEbKGohuNNkHdLS8kmg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-10-14 14:21   ` John MacFarlane [this message]
     [not found]     ` <20131014142109.GA9935-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2013-10-14 14:42       ` Václav Zeman
2013-10-14 14:59       ` Joost Kremers

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=20131014142109.GA9935@Johns-MacBook-Pro.local \
    --to=fiddlosopher-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).