summaryrefslogtreecommitdiffstats
path: root/2021/talks/org-outside.md
diff options
context:
space:
mode:
Diffstat (limited to '2021/talks/org-outside.md')
-rw-r--r--2021/talks/org-outside.md25
1 files changed, 24 insertions, 1 deletions
diff --git a/2021/talks/org-outside.md b/2021/talks/org-outside.md
index 30ee1d9a..c10cd761 100644
--- a/2021/talks/org-outside.md
+++ b/2021/talks/org-outside.md
@@ -37,6 +37,19 @@ information.
# Discussion
+Pad:
+
+- Q1: Great talk. I have been following your work on PIM for a while
+ (incl. a sneak read of your dissertation:-). Just curious, what
+ would you personally use Orgdown for?
+ - A: Oh, this would be a very loooong answer. I think you want to
+ visit:
+ - <https://karl-voit.at/tags/emacs/> and go to other pages
+ like <https://karl-voit.at/2019/09/25/using-orgmode/>
+ - Basically, Orgdown is already part of my workflows since
+ years: <https://github.com/novoid/lazyblorg/> or
+ <https://github.com/novoid/appendorgheading/> and much more.
+
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)?
@@ -98,7 +111,17 @@ IRC: (nick: publicvoit)
- 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
-
+
+
+Links and other notes:
+
+- The article from 2017 that started the whole discussion: \"Org Mode
+ Is One of the Most Reasonable Markup Languages to Use for Text\"
+ <https://karl-voit.at/2017/09/23/orgmode-as-markup-only/>
+- Orgdown homepage: <https://gitlab.com/publicvoit/orgdown>
+- Orgdown motivation article:
+ <https://karl-voit.at/2021/11/27/orgdown/>
+
# Outline
- The term Org mode stands for different things