public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "John Gabriele" <jgabriele-97jfqw80gc6171pxa8y+qA@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Tildas or backticks for fenced code blocks
Date: Tue, 05 Jul 2022 11:50:06 -0400	[thread overview]
Message-ID: <d1d388b1-0aa3-43aa-89fc-e44653815c3f@www.fastmail.com> (raw)
In-Reply-To: <m235fnywju.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>

I use the tildes because I think they look better. They're vertically in the middle of the glyph.

Backticks are too high up, and so at the top of the fenced block look like they're floating too high up, and at the bottom are cuddled up too tight. They also make it harder to see where leading or trailing blank lines are.

-- John

On Wed, Jun 29, 2022, at 5:44 PM, John MacFarlane wrote:
> That is right.  I discussed the idea on the old markdown-discuss
> listserv with other markdown implementers at the time, and we
> agreed on tildes.
>
> I believe that at least pandoc and PHP markdown implemented this
> syntax.
>
> Then GitHub came out with their own fenced code block syntax
> using backticks (without discussing this or even perhaps being
> aware of the tilde syntax).  This isn't ideal, really, because it
> introduces a syntactic ambiguity between inline code and code
> blocks, but it has a certain naturalness, and doesn't require
> pressing the shift key.  At any rate, it caught on, so pandoc
> allowed this form too.  I think the tilde form is rarely used
> any more.
>
> Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org> writes:
>
>> name name <ivan20151013-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>
>>> I'm new to Pandoc. From what I have read in the manual, it seems the
>>> preferred way to create fenced code blocks is to use tildas, not
>>> backticks:
>>>
>>>    ~~~
>>>    fenced code block
>>>    ~~~
>>>
>>> What is the exact reason for this?
>>
>> I believe that fenced code blocks where first introduced in pandoc with
>> syntax using tildes; other tools then followed suit, but used the
>> now-popular backticks syntax. At least I seem to remember reading
>> something along these lines, but I might be completely wrong.
>>
>> -- 
>> 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/87a69vbbar.fsf%40zeitkraut.de.
>
> -- 
> 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/m235fnywju.fsf%40johnmacfarlane.net.


      parent reply	other threads:[~2022-07-05 15:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29 17:00 name name
     [not found] ` <64334345-f5c7-4871-b3d0-5911b1d49cb5n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-29 17:43   ` Albert Krewinkel
     [not found]     ` <87a69vbbar.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-06-29 21:44       ` John MacFarlane
     [not found]         ` <m235fnywju.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2022-07-05 15:50           ` John Gabriele [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=d1d388b1-0aa3-43aa-89fc-e44653815c3f@www.fastmail.com \
    --to=jgabriele-97jfqw80gc6171pxa8y+qa@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).