From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Proposal: default to ATX-style headings in markdown output
Date: Fri, 04 Sep 2020 08:00:43 +0200 [thread overview]
Message-ID: <878sdqxer8.fsf@zeitkraut.de> (raw)
In-Reply-To: <39d45d2d-952a-4af3-8f3b-e9af667f2a49n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Pranesh Prakash writes:
> I guess I'm in the minority — in that I don't always use atx-style
> headings. I switch between atx-[1] and setext-style headings depending on
> the context. In e-mails and in (plaintext) e-mail newsletters, I generally
> use setext-style headings since those are easily understood even by those
> who don't know about Markdown/atx. However, in all my other writings, I
> use atx-style headings. I would support making atx-style headings the
> default.
I second this. Setext headers are great whenever it is likely that the
text will be read as unrendered plaintext. It's still what I prefer for
README files. But given the growing popularity of atx headers, it would
seem reasonable to make the latter the default.
--
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
--
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/878sdqxer8.fsf%40zeitkraut.de.
next prev parent reply other threads:[~2020-09-04 6:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 15:57 John MacFarlane
2020-09-03 16:06 ` Anton Shepelev
[not found] ` <20200903190619.e924ccd888daca8cef4460ea-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-09-03 16:21 ` BPJ
[not found] ` <CADAJKhAM7MbY3GExs38hrApHrSntg87X04sKbJTnSb1bWzQPGA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-09-03 16:51 ` Leonard Rosenthol
[not found] ` <CALu=v3LKDJpsEL-WoK8vre3uJAgrWrOeaRM0gy4RH1+kLm8Qkg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-09-03 17:11 ` Joseph Reagle
[not found] ` <m2blimyhsb.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-09-03 19:07 ` Dmitry Safronov
[not found] ` <3baeae13-8eca-4464-ac84-84c988f7a91do-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-09-04 16:09 ` John MacFarlane
2020-09-03 20:28 ` Denis Maier
[not found] ` <586af284-c52b-d1df-04d2-96fd2f52d8e3-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
2020-09-03 20:37 ` MyriaCore
[not found] ` <d8df1ef0-7a5a-4a07-8758-909a262e6119n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-09-03 21:09 ` Pranesh Prakash
[not found] ` <39d45d2d-952a-4af3-8f3b-e9af667f2a49n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-09-04 6:00 ` Albert Krewinkel [this message]
2020-09-04 8:54 ` Anton Shepelev
2020-09-04 9:42 ` Anton Shepelev
[not found] ` <20200904124240.5d93260af90b10618677d8cb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-09-04 10:44 ` BPJ
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=878sdqxer8.fsf@zeitkraut.de \
--to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@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).