summaryrefslogtreecommitdiffstats
path: root/2020/schedule/14.md
diff options
context:
space:
mode:
Diffstat (limited to '2020/schedule/14.md')
-rw-r--r--2020/schedule/14.md34
1 files changed, 2 insertions, 32 deletions
diff --git a/2020/schedule/14.md b/2020/schedule/14.md
index ed9f6f68..b1bd3d71 100644
--- a/2020/schedule/14.md
+++ b/2020/schedule/14.md
@@ -5,39 +5,9 @@ Back to the [[schedule]]
Previous: <a href="/2020/schedule/13">Experience Report: Steps to "Emacs Hyper Notebooks"</a>
Next: <a href="/2020/schedule/15">Moving from Jekyll to OrgMode, an experience report</a>
+Saturday, Nov 28 2020, 2:18 PM - 2:38 PM EST / 11:18 AM - 11:38 AM PST / 7:18 PM - 7:38 PM UTC / 8:18 PM - 8:38 PM CET / 3:18 AM - 3:38 AM +08
-# Literate Programming in Emacs Org-Mode
-Saturday, Nov 28 2020, 2:18 PM - 2:38 PM EST / 11:18 AM - 11:38 AM PST / 7:18 PM - 7:38 PM UTC / 8:18 PM - 8:38 PM CET / 3:18 AM - 3:38 AM +08
-Adam Ard
-
-Org mode, among its numerous features, has the ability to do full
-literate programming (with tangling and weaving the way Donald Knuth
-originally intended). As a programmer, you can work comfortably,
-completely inside an org-mode buffer. When you are ready, emacs will
-generate the appropriate documentation and source code files for you.
-If you are a lone emacs user on your project, simply commit these
-exported files and keep your org file to yourself &#x2013; no one is the
-wiser.
-
-Watch "Literate Programming in Emacs Org-mode" to learn how you can
-annotate code snippets in an org file so they can be automatically
-exported to their proper locations in your source tree. Keep
-important information about your project where it should be: right
-next to the code itself. Not as ugly, out-of-date notes sitting
-behind comment characters in your source files, but front and center
-in well-formatted markdown and pdf files.
-
-And, for advanced use cases, see how you can even use a full-fledged
-macro processor like m4 to personalize your workflow even more.
-Literate programming on steroids!
-
-I'll walk you through the whole process, starting from an empty
-project README.org to a simple example that generates source and
-documentation.
-
-
-
-
+[[!inline pages="../info/14" raw="yes"]]
Back to the [[schedule]]
Previous: <a href="/2020/schedule/13">Experience Report: Steps to "Emacs Hyper Notebooks"</a>