Add support for posting with Markdown syntax
### Pitch Requests to add support for posting with Markdown formatting has come up many times in the past, so this is a proposal to formalize the recent efforts. I'm not against other forms of markup formatting, but am focusing this issue specifically on Markdown. My understanding is that Markdown support has not been fully approved or denied. The previous PR in #10787 (based on issue #853) seems to have been rejected due to issues in the implementation (and a somewhat derailed discussion). Issues #13544 and #21643 are similar, but cover subsections of this larger topic. _I consider this a continuation of the conversation in #18958._ Two main points stand out: - **Is there general agreement to add Markdown support?** I think clearing up this question first will avoid the conflicts that appeared in the rejected PR. - **If yes, how should Markdown be implemented?** - _Markdown flavour:_ Depending on the user, they might be coming from [CommonMark](https://commonmark.org/), the [GitHub-Flavoured derivative](https://github.github.com/gfm/), [Reddit](https://reddit.com/wiki/markdown) (where New Reddit is different from Old), [Misskey](https://misskey-hub.net/en/docs/features/mfm.html), [Redcarpet](https://github.com/vmg/redcarpet), or the [original spec](https://daringfireball.net/projects/markdown/syntax), to name a few. One of these needs to be selected to avoid issues from mixing them. - _Scope:_ Supporting all of Markdown would be a massive effort and massively increas
Posted by jessicarod7 on Mar 6, 2023, 5:17 AM
Tags
Related issues
- Add 65536 size support for maps
- TypeScript 7.1 Iteration Plan
- nvim-treeconfig: upstream nvim-treesitter
- Add the "action" and "method" attributes to <button>
- [FEATURE] Support multiple Connector accounts (same connector, different accounts) in Claude and Claude Code on the web (claude.ai/code)
- > We were imposed GitHub for so many exercises!
Raise real-world problems, find people facing the same issue, and discuss solutions.2,500 issues0 comments
support (Software)
Add 65536 size support for maps
TypeScript 7.1 Iteration Plan
nvim-treeconfig: upstream nvim-treesitter
Add the "action" and "method" attributes to <button>
[FEATURE] Support multiple Connector accounts (same connector, different accounts) in Claude and Claude Code on the web (claude.ai/code)
> We were imposed GitHub for so many exercises!
Add support for Visual Studio 2026 Integration
Support for Helm v4
Add support for posting with Markdown syntax
### Pitch Requests to add support for posting with Markdown formatting has come up many times in the past, so this is a proposal to formalize the recent efforts. I'm not against other forms of markup formatting, but am focusing this issue specifically on Markdown. My understanding is that Markdown support has not been fully approved or denied. The previous PR in #10787 (based on issue #853) seems to have been rejected due to issues in the implementation (and a somewhat derailed discussion). Issues #13544 and #21643 are similar, but cover subsections of this larger topic. _I consider this a continuation of the conversation in #18958._ Two main points stand out: - **Is there general agreement to add Markdown support?** I think clearing up this question first will avoid the conflicts that appeared in the rejected PR. - **If yes, how should Markdown be implemented?** - _Markdown flavour:_ Depending on the user, they might be coming from [CommonMark](https://commonmark.org/), the [GitHub-Flavoured derivative](https://github.github.com/gfm/), [Reddit](https://reddit.com/wiki/markdown) (where New Reddit is different from Old), [Misskey](https://misskey-hub.net/en/docs/features/mfm.html), [Redcarpet](https://github.com/vmg/redcarpet), or the [original spec](https://daringfireball.net/projects/markdown/syntax), to name a few. One of these needs to be selected to avoid issues from mixing them. - _Scope:_ Supporting all of Markdown would be a massive effort and massively increas
Comments (0)
No comments yet. Start the discussion.