Skip to main content
8 events
when toggle format what by license comment
Aug 8, 2022 at 19:25 history edited Yaakov EllisStaffMod CC BY-SA 4.0
completed
Jul 14, 2022 at 14:43 comment added Makyen @TylerMcEntee That you don't insure round trips from Markdown->rich text->Markdown always preserve things exactly as they were in the Markdown source is a huge portion of the fundamental problems with this editor. If you were insuring preservation in all cases, then a large number of your bugs wouldn't exist and people would be substantially more comfortable using this editor. Combined with having no preview other than switching to rich text mode (i.e. that to preview requires corrupting the Markdown) is one of the major reasons there's been such a negative response to this editor.
Jul 13, 2022 at 11:28 history edited Yaakov EllisStaffMod CC BY-SA 4.0
review and gh link
Jul 13, 2022 at 10:49 comment added bad_coder @TylerMcEntee Addind a fence in rich text is likely the only chance because per CommonMark specification one empty line on the same indentation level does not break a code block.
Jul 12, 2022 at 18:24 comment added Tyler McEntee Mod Either way, we still should be able to insure we preserve that indentation-free line in between the code blocks when round-tripping between Markdown and Rich Text modes.
Jul 12, 2022 at 18:23 comment added Tyler McEntee Mod I wonder if a more robust solution here would be to serialize the code blocks into Markdown with the triple-backtick codeblocks (```) instead of pure whitespace indentation. The code block button in Markdown mode already does this, and has the added benefit of being able to specify the syntax highlighting manually (```css).
Jul 12, 2022 at 15:03 comment added ouflak Wasn't this, or something very much like this, fixed in the original alpha release?
Jul 12, 2022 at 14:23 history answered Ryan M CC BY-SA 4.0