diff options
| author | Sacha Chua <sacha@sachachua.com> | 2021-12-02 01:23:52 -0500 |
|---|---|---|
| committer | Sacha Chua <sacha@sachachua.com> | 2021-12-02 01:23:52 -0500 |
| commit | 3b6a2c161825236f442727107b02d30a4b4c0c70 (patch) | |
| tree | d604edeb2cfca73cd654abde2745a51f831a2540 /2021/talks/org-outside.md | |
| parent | 532bc5cda6dc0f094e9adcfdadfdc7bf435779f0 (diff) | |
| download | emacsconf-wiki-3b6a2c161825236f442727107b02d30a4b4c0c70.tar.xz emacsconf-wiki-3b6a2c161825236f442727107b02d30a4b4c0c70.zip | |
IRC notes from day 2
Diffstat (limited to '2021/talks/org-outside.md')
| -rw-r--r-- | 2021/talks/org-outside.md | 14 |
1 files changed, 13 insertions, 1 deletions
diff --git a/2021/talks/org-outside.md b/2021/talks/org-outside.md index 0df228e3..f6dd2e6c 100644 --- a/2021/talks/org-outside.md +++ b/2021/talks/org-outside.md @@ -56,7 +56,19 @@ IRC nick: publicvoit - already uses the ".org.txt" file extension, so that tools that don't otherwise support the org file type will at the very least read them - sorry to have missed out on the discussion during your talk, but I'm extremely interested in getting org working outside elisp (re: https://github.com/tgbugs/laundry/tree/next). I started there long ago, at this point the issues that really need standardization is org-babel, but in order to do that we need the syntax settled, which has turned out to be a _lot_ of work - having orgdown as a way to talk about files that have org syntax seems like it is a critical piece for effective outreach - +- would it be worth considering a decoupling of the "orgdown" proposal into 1) just a proposal to rename "org" the markup as "orgdown" (vs "org-mode" for the piece of software running in Emacs), and 2) all the rest as in the levels/etc? Just to not put the first at risk of non-adoption because of the contents of the second? There seems to be a lot of positive sentiment towards solving #1 for sure. + - orgdown is not org, the markup + - orgdown is lightweight org, it does not have all the features + - In general I agree, there will be issues with how to approach the levels + - publicvoit: Valid approach but this train has left the station already by the decision of myself to provide OD1 to the public this weekend. +- To be fair, I personally don't think adding tiers to org-mode makes much sense + - We should rather have a feature matrix for stuff like pandoc to check against + - developing the test suite will get us there, and then we can have the discussion about how to market the levels +- I think we could adopt orgdown almost immediately without issue +- I don't really see a big issue with org-mode vs. org vs. orgWHATEVER though + - there are major search and discovery issues with bare "org" + - I tend to use "org syntax" at the moment, but it isn't catchy enough + # Outline - The term Org mode stands for different things |