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/tech.md | 2 ++ 1 file changed, 2 insertions(+) (limited to '2021/talks/tech.md') diff --git a/2021/talks/tech.md b/2021/talks/tech.md index 6a26281c..3ec253b7 100644 --- a/2021/talks/tech.md +++ b/2021/talks/tech.md @@ -27,6 +27,7 @@ org-treeslide to write and present technical documentation with style. # Discussion BBB: + - Have you encountered any push-back from people requesting the documentation who are of the opinion that only a Word document will do? - Jan: Not really, I tend to deliver the PDFs only. If more is needed, I expect I'd make a docker container with emacs in it, so people can export the org-file to PDF themselves. - The main problem I have is that effectively they end up branching it in order to use Word's change tracking, and there is no reverse path. @@ -39,6 +40,7 @@ BBB: - Jan: Hold their hands, be kind, small baby steps :) IRC: (nick: jan-ypma) + - I use restclient everyday, but never thought about using it from code blocks, duh! Very interesting talk! - This is a good demo, I've found org-babel to be a really amazing glue language for stuff that's sort of annoying to automate otherwise. - Thanks! :) So the fonts of the current talk are: Fixed pitch (serif): New Heterodox Mono, Variable pitch (serif): ETBembo -- cgit v1.2.3