From f887a26d70b871db28ce2fad74b88540fe6e7e79 Mon Sep 17 00:00:00 2001 From: Leo Vivier Date: Thu, 2 Dec 2021 16:37:13 +0100 Subject: Add missing newlines for discussions --- 2021/talks/org-outside.md | 3 +++ 1 file changed, 3 insertions(+) (limited to '2021/talks/org-outside.md') diff --git a/2021/talks/org-outside.md b/2021/talks/org-outside.md index c0799e21..30ee1d9a 100644 --- a/2021/talks/org-outside.md +++ b/2021/talks/org-outside.md @@ -38,6 +38,7 @@ information. # Discussion BBB: + - Hi Karl. I was wondering, does the specification make any restrictions with regard to indentation levels or hard vs. soft line breaks? Do you have any type of test suites that an implementation can use to be "certified" as orgdown(1)? - Are you worried about the different levels of orgdown leading to the same confusing situation we have with Markdown? - I think the ability to indicate that some tools are compatible with org is fantastic! @@ -60,12 +61,14 @@ BBB: - neorg seems to be an expanded org-mode syntax and is not compatible with orgmode BBB feedback: + - I think no tags is a good idea, very implementation specific - I think it's a fantastic idea, and the initial proposal is very good! - i need to go, but thanks for introducing the idea, excited to see where it goes! - Thanks for your proposal. I really hope it will work out. IRC: (nick: publicvoit) + - is there a tree-sitter parser for orgdown already? :P - it seems to me that as org evolves, either orgdown eventually becomes incompatible with org or org is prevented from changing because it would break orgdown. I guess backcompat with existing org documents constrains org-mode this way already, though - what level would you call github's implementation is? -- cgit v1.2.3