summaryrefslogtreecommitdiffstats
path: root/2021
diff options
context:
space:
mode:
authorLeo Vivier <zaeph@zaeph.net>2021-12-02 16:33:34 +0100
committerLeo Vivier <zaeph@zaeph.net>2021-12-02 16:33:34 +0100
commit9c1022e33f7382331f8622084379088d9e8bce9a (patch)
tree5c5b83b45675e1d5b3b420c72e9bd3412eb33750 /2021
parent36a04851a6bbbe9eb3aef74dade698ca7700fd43 (diff)
downloademacsconf-wiki-9c1022e33f7382331f8622084379088d9e8bce9a.tar.xz
emacsconf-wiki-9c1022e33f7382331f8622084379088d9e8bce9a.zip
Add BBB logs
Diffstat (limited to '2021')
-rw-r--r--2021/talks/maintainers.md22
1 files changed, 10 insertions, 12 deletions
diff --git a/2021/talks/maintainers.md b/2021/talks/maintainers.md
index 109307e9..8a542316 100644
--- a/2021/talks/maintainers.md
+++ b/2021/talks/maintainers.md
@@ -22,29 +22,27 @@ BBB:
- agreed, I appreciate that the list isn't split.
- vastly simplifies workflows.
-- Wouldn't they be missing the key part, Emacs?
-- (ah, i understood forking for a different toolset, vs markdown-based org-mode on Emacs, apologies)
-- Bastien Guerry: <https://list.orgmode.org/87y2jvkeql.fsf@gnu.org/>
+- (Missing context) Wouldn't they be missing the key part, Emacs?
+ - Questioner: (ah, i understood forking for a different toolset, vs markdown-based org-mode on Emacs, apologies)
+ - Bastien Guerry: <https://list.orgmode.org/87y2jvkeql.fsf@gnu.org/>
- devil's advocate to Karl's point now though: is that from habit?
-- link syntax in markdown is impossible to remember
+- link syntax in markdown is impossible to remember for simplifying e.g. keyword syntax can be made regular. consistency across levels is extremely hard due to interactions between features, in part because you only encounter those much later in implementation. another part of the issue is that Org has more features than pandoc markdown so it is sometimes unrepresentable.
+- interestingly Timothy has solved most of the markdown &> org
- plain orgmode is easy to visualize. with markdown you need to export this if you have many md lines. org tables is a clear example of the visualization
-- I think the argument of the best syntax is a hard battle to fight, but where the bar is clear is the software (org-mode) and what it can do with it, as of today. for simplifying e.g. keyword syntax can be made regular. consistency across levels is extremely hard due to interactions between features, in part because you only encounter those much later in implementation. another part of the issue is that Org has more features than pandoc markdown so it is sometimes unrepresentable.
-- interestingly Timothy has solved most of the markdown -&gt; org
+- I think the argument of the best syntax is a hard battle to fight, but where the bar is clear is the software (org-mode) and what it can do with it, as of today.
- FYI org-sidebar provides a backlinks tool
- Backlinks! Yes!
- Backlinks for me: <https://karl-voit.at/2020/07/22/org-super-links/>
- was going to say : many of the org-roam features should make their way into core org-mode eventually
- how to manage and cache other types of data that are similar to backlinks
- something like org-id caching, you mean?
-- alphapapa: not quite, more things that we don't want to put in the org file directly
-- e.g. babel caches for huge pieces of data
+- alphapapa: not quite, more things that we don't want to put in the org file directly; e.g. babel caches for huge pieces of data
- id caching for performance would be great, some of the vizualisation things are very interesting too
-- it is a hard problem
+ - it is a hard problem
+
+BBB feedback:
- Thank you for taking the time to share your accumulated wisdom with us, Bastien :)
-- Thanks Bastien!
-- thank you!
- merci Bastien!
-- Bastien Guerry: Bye all !
IRC: