public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Formatting to Markdown inserts space indentation in list items
Date: Tue, 17 Oct 2017 08:27:09 -0400	[thread overview]
Message-ID: <a4af9a42-f450-839e-f6ab-48d4819ce355@usa.net> (raw)
In-Reply-To: <1555A65C-6069-41DC-9008-87431E6F6EF0-cFyOE3ROWdBBDgjK7y7TUQ@public.gmane.org>

On 10/17/17 1:29 AM, Will Faught wrote:
> OK, thanks.
> 
> I think it’s a mistake to always do it that way. One space is far more preferable when writing a long list by hand.

It also causes problems when you try to do multi-level lists.  However, 
if I may make a suggestion:

Write it with one space, and then format with Pandoc.  Then they'll 
always be the same amount of space, even if you accidentally hit the 
space bar twice someplace.  ;)

Daniel T. Staal

-- 
---------------------------------------------------------------
This email copyright the author.  Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes.  This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------

-- 
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/a4af9a42-f450-839e-f6ab-48d4819ce355%40usa.net.
For more options, visit https://groups.google.com/d/optout.


      parent reply	other threads:[~2017-10-17 12:27 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
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 [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=a4af9a42-f450-839e-f6ab-48d4819ce355@usa.net \
    --to=dstaal-jdbf3xikgs8@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).