Closed Fang- closed 5 years ago
Udon is not markdown, and is intentionally trying to be simpler in a number of incompatible ways. (In this case, commonmark-spec parsing of nested foo bar is admittedly pretty hairy; but I generally agree that udon should never have been introduced and we should have stuck with real .md)
On Tue, Apr 16, 2019 at 1:37 PM Fang notifications@github.com wrote:
Expected behavior is what you find on Github and most other places that support markdown-style formatting, where and are distinguished by the amount of formatting characters around a string, rather than distinguishing between * and _. The fact that udon deviates from that is confusing and frustrating.
In other words:
Current: this --> this this --> this
Expected/desired: this, this --> this this, this --> this
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/urbit/arvo/issues/1149, or mute the thread https://github.com/notifications/unsubscribe-auth/ABxXhhAxiBNOcF98WoplhNvMSp1KcGkDks5vhjSCgaJpZM4czqE7 .
I also perceived this to be an intentional simplification
Markup in Keybase chat behaves similarly. I dig it.
@Fang- Want to do anything with this one, i.e. propose a change more formally? Otherwise my closing finger is getting itchy..
Seems like most others are fine with the way things are now. We can reopen if it comes up again.
Expected behavior is what you find on Github and most other places that support markdown-style formatting, where
<strong>
and<em>
are distinguished by the amount of formatting characters around a string, rather than distinguishing between*
and_
. The fact that udon deviates from that is confusing and frustrating.In other words:
Current:
_this_
--> this*this*
--> thisExpected/desired:
*this*, _this_
--> this**this**, __this__
--> this