From: John MACFARLANE <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Formatting to Markdown inserts space indentation in list items
Date: Mon, 16 Oct 2017 14:55:18 -0700 [thread overview]
Message-ID: <20171016215518.GA21256@protagoras> (raw)
In-Reply-To: <b2690c61-9b86-44f6-bb00-96df411c9ba5-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
There's no way to retain all the details of the original
formatting. Everything goes via an intermediate
representation of a structured document, which does not
store details like how many spaces between the bullet and
the text...
There's actually good reason to format the way we do, since
it makes everything line up when you obey the four-space
rule:
- beginning paragraph
second paragraph of list
- sublist
Obeying the four-space rule is what you should do if you
want your document to be compatible with the most Markdown
implementations.
+++ will.faught-cFyOE3ROWdBBDgjK7y7TUQ@public.gmane.org [Oct 16 17 14:00 ]:
> For example, when formatting this:
> ```
> - a
> - b
> - c
> ```
> I get this:
> ```
> - a
> - b
> - c
> ```
> where there are now 3 spaces between the hyphen and the bullet text
> Instead of the original 1 space.
> How do I either keep the original spacing, or control the number of
> spaces it uses (I want 1 space)?
> It seems to happen when formatting to any Markdown flavor.
>
> --
> 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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to
> [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> [3]https://groups.google.com/d/msgid/pandoc-discuss/b2690c61-9b86-44f6-
> bb00-96df411c9ba5%40googlegroups.com.
> For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
> 1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 3. https://groups.google.com/d/msgid/pandoc-discuss/b2690c61-9b86-44f6-bb00-96df411c9ba5-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 4. https://groups.google.com/d/optout
next prev parent reply other threads:[~2017-10-16 21:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 21:00 will.faught-cFyOE3ROWdBBDgjK7y7TUQ
[not found] ` <b2690c61-9b86-44f6-bb00-96df411c9ba5-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-16 21:55 ` John MACFARLANE [this message]
2017-10-16 22:39 ` Will Faught
[not found] ` <D89DE061-372E-4D75-8706-9DCC4CF2621A-cFyOE3ROWdBBDgjK7y7TUQ@public.gmane.org>
2017-10-17 3:52 ` John MacFarlane
[not found] ` <20171017035228.GB57897-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-10-17 5:29 ` Will Faught
[not found] ` <1555A65C-6069-41DC-9008-87431E6F6EF0-cFyOE3ROWdBBDgjK7y7TUQ@public.gmane.org>
2017-10-17 12:27 ` Daniel Staal
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=20171016215518.GA21256@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).