[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Using backticks for the inline code delimeter?
From: |
Tim Cross |
Subject: |
Re: Using backticks for the inline code delimeter? |
Date: |
Thu, 01 Apr 2021 09:38:17 +1100 |
User-agent: |
mu4e 1.5.11; emacs 27.2.50 |
"Dr. Arne Babenhauserheide" <arne_bab@web.de> writes:
> George Mauer <gmauer@gmail.com> writes:
>> - lists with dashes, org supports that just fine
>
> or stars (not possible with org) or plus (in org).
>
>> *bold text* with stars, again org already does this
>
> Note that this does not match markdown: Markdown uses *emphasis* and
> **strong**.
>
>> `backtick code`, org doesn't handle this and actually uses the tilde as a
>> delimeter which is extra jarring since its a strikethrough in many chat apps
>
> tilde or equals.
>
> - list
> *bold*
> =code=
>
> Adding more syntax is a slippery slope, because then `foo` can never be
> used for anything else, and there is a limited amount of usable syntax
> elements.
>
Yes, I think this is potentially a bad idea. Org parsing is already slow
enough without adding yet more syntax and font-locking complexity.
I also suspect this is not as simple as just adding this to org parsing
- all backends and many contributed packages would likely also need to
be updated to understand the new syntax. So probably not a trivial
change and a change which is likely to have real impact wrt backwards
compatibility.
Part of the issue here is that there is no markdown 'standard'. There
are a number of markdown 'flavors' or dialects. Org is just another one
(and one of the older ones at that).
--
Tim Cross
Re: Using backticks for the inline code delimeter?, Bill Burdick, 2021/03/31
Re: Using backticks for the inline code delimeter?, Greg Minshall, 2021/03/31