From: BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
Cc: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: general attributes and yaml metadata block
Date: Mon, 24 Aug 2020 19:50:09 +0200 [thread overview]
Message-ID: <CADAJKhCYF3ZhaPzF5VWZKqygzfK3YqZn=-dZZZ-yneh6Y-qrpw@mail.gmail.com> (raw)
In-Reply-To: <m2o8n0x9s8.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]
Den mån 24 aug. 2020 18:56John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> skrev:
>
> > Do you have any particular ones in mind. I guess that at the moment I'm
> > most afraid of losing `four_space_rule` since it is so to speak a
> > compatibility extension. OTOH maybe if I consistently use steps of 4 in
> my
> > source (which I already do, e.g. 3 spaces after a list bullet) I won't
> > notice much difference.
>
> I think that's right, except in unusual cases (e.g., list numbers
> greater than two digits).
>
> 999. hello
> four-space rule says that content starts here
>
> 999. hello
> commonmark says it starts here.
>
I'm afraid I will never get used to that! The four-space rule, or rather
hitting tab, has become part of my muscle memory. I'm probably not the only
one.
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CADAJKhCYF3ZhaPzF5VWZKqygzfK3YqZn%3D-dZZZ-yneh6Y-qrpw%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 2124 bytes --]
prev parent reply other threads:[~2020-08-24 17:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 12:07 Christian Müller
[not found] ` <a0460a16-04eb-4ff8-8159-4a22138967b7o-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-08-21 20:51 ` John MacFarlane
[not found] ` <m2h7svafjy.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-08-22 8:34 ` ch_...-S0/GAf8tV78@public.gmane.org
[not found] ` <b88f4db2-e711-41b5-8223-87f90447753fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-08-22 10:41 ` mb21
2020-08-22 16:08 ` John MacFarlane
[not found] ` <m24kou8xzd.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-08-22 16:52 ` BPJ
[not found] ` <CADAJKhAofn83Rb6P1k7eqoYEwXrKsyH7e0mJ+AJFKVe8XDnehw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-08-22 18:07 ` John MacFarlane
[not found] ` <m2v9ha7dwo.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-08-24 9:59 ` BPJ
[not found] ` <CADAJKhA_NN8XUq8GXUJn4ObasyRQrw5inXgtatWvwRPOcSmzoQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-08-24 16:56 ` John MacFarlane
[not found] ` <m2o8n0x9s8.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-08-24 17:50 ` BPJ [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='CADAJKhCYF3ZhaPzF5VWZKqygzfK3YqZn=-dZZZ-yneh6Y-qrpw@mail.gmail.com' \
--to=melroch-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=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).