From c9242e20ccc9f39774dd6272c53a927b5311520a Mon Sep 17 00:00:00 2001 From: Sacha Chua Date: Tue, 10 Nov 2020 22:45:51 -0500 Subject: Change literate programming talk to README-Driven Design --- 2020/info/14.md | 4 +-- 2020/schedule-details.txt | 2 +- 2020/submissions.md | 92 +++++++++++++++++++++++------------------------ 2020/submissions.org | 6 ++-- 4 files changed, 52 insertions(+), 52 deletions(-) (limited to '2020') diff --git a/2020/info/14.md b/2020/info/14.md index a49b302e..ffbb6d96 100644 --- a/2020/info/14.md +++ b/2020/info/14.md @@ -1,4 +1,4 @@ -# Literate Programming in Emacs Org-Mode +# README-Driven Design Adam Ard Org mode, among its numerous features, has the ability to do full @@ -10,7 +10,7 @@ If you are a lone emacs user on your project, simply commit these exported files and keep your org file to yourself – no one is the wiser. -Watch "Literate Programming in Emacs Org-mode" to learn how you can +Watch "README-Driven Design" 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 diff --git a/2020/schedule-details.txt b/2020/schedule-details.txt index 7b44b328..da0c2fe6 100644 --- a/2020/schedule-details.txt +++ b/2020/schedule-details.txt @@ -20,7 +20,7 @@ 1:29 PM 1:49 PMthe org-gtd package: opinions about Getting Things DoneAldric 1:52 PM 2:02 PMOne Big-ass Org File or multiple tiny ones? Finally, the End of the debate!Leo Vivier 2:05 PM 2:15 PMExperience Report: Steps to "Emacs Hyper Notebooks"Joseph Corneli, Raymond Puzio, and Cameron Ray Smith - 2:18 PM 2:38 PMLiterate Programming in Emacs Org-ModeAdam Ard + 2:18 PM 2:38 PMREADME-Driven DesignAdam Ard 2:41 PM 2:51 PMMoving from Jekyll to OrgMode, an experience reportAdolfo Villafiorita 2:54 PM 3:14 PMOrg-roam: Presentation, Demonstration, and What's on the HorizonLeo Vivier 3:17 PM 3:37 PMOrg-mode and Org-Roam for Scholars and ResearchersNoorah Alhasan diff --git a/2020/submissions.md b/2020/submissions.md index f2bcc2d1..5a09b927 100644 --- a/2020/submissions.md +++ b/2020/submissions.md @@ -7,32 +7,32 @@ You can check out the Org Mode source for this page by following the [editing in # Table of Contents -- [Actions](#org3b08519) -- [Tables](#org6935e90) - - [Overall](#org52370f5) - - [By slot](#org79bb67d) - - [Saturday](#orgbcf4427) - - [Sunday](#org2cd348d) - - [Table for all talks](#org5e7829c) -- [Talks](#org1a9b6a6) - - [NOVEMBER 28 (Saturday)](#org4c74d5f):sat: - - [9:00 - 9:30 Opening remarks](#orgc0f5be6) - - [9:30 - 12:00 User talks](#org95c98eb):morning: - - [12:00 - 13:00 Lunch](#org25a0c47) - - [13:00 - 16:30 Afternoon talks](#org4366225):afternoon: - - [16:30 - 17:00 Closing remarks](#orgaeceb8b) - - [NOVEMBER 29 (Sunday)](#org7fe4148):sun: - - [9:00 - 9:10 Opening remarks](#org911ba32) - - [9:10 - 12:00 Morning talks](#orgb4dfc5b):morning: - - [12:00 - 13:00 Lunch](#org8518390) - - [13:00 - 16:30 Afternoon talks](#org1c356e2):afternoon: - - [16:30 - 17:00 Closing remarks](#org935b91b) +- [Actions](#org46d1a44) +- [Tables](#org48f0fff) + - [Overall](#org1b79c1a) + - [By slot](#orgc706356) + - [Saturday](#org1062f77) + - [Sunday](#org1765449) + - [Table for all talks](#org952919d) +- [Talks](#org4648599) + - [NOVEMBER 28 (Saturday)](#org458a793):sat: + - [9:00 - 9:30 Opening remarks](#org3e8be92) + - [9:30 - 12:00 User talks](#org0ae6710):morning: + - [12:00 - 13:00 Lunch](#org42d0c78) + - [13:00 - 16:30 Afternoon talks](#org7fb22ea):afternoon: + - [16:30 - 17:00 Closing remarks](#orga9c5a06) + - [NOVEMBER 29 (Sunday)](#orgf72903b):sun: + - [9:00 - 9:10 Opening remarks](#orgd6daa72) + - [9:10 - 12:00 Morning talks](#org8512848):morning: + - [12:00 - 13:00 Lunch](#org20510d0) + - [13:00 - 16:30 Afternoon talks](#org3b7bf07):afternoon: + - [16:30 - 17:00 Closing remarks](#orgf450002) - [Code](#talk37) - - [Planning](#org4a4216b) - - [Generate schedule file](#orgb0d6323) + - [Planning](#orgf5de6c2) + - [Generate schedule file](#org9c7b0ca) - + # Actions @@ -45,12 +45,12 @@ To update the information included in the individual talk page, execute the buffer, update the talk's info/TALKID.md file. - + # Tables - + ## Overall @@ -182,12 +182,12 @@ execute the buffer, update the talk's info/TALKID.md file. - + ## By slot - + ### Saturday @@ -437,7 +437,7 @@ execute the buffer, update the talk's info/TALKID.md file. - + ### Sunday @@ -642,7 +642,7 @@ execute the buffer, update the talk's info/TALKID.md file. - + ## Table for all talks @@ -966,22 +966,22 @@ execute the buffer, update the talk's info/TALKID.md file. - + # Talks - + ## NOVEMBER 28 (Saturday) :sat: - + ### 9:00 - 9:30 Opening remarks - + ### 9:30 - 12:00 User talks :morning: @@ -1718,12 +1718,12 @@ execute the buffer, update the talk's info/TALKID.md file. fair use. - + ### 12:00 - 13:00 Lunch - + ### 13:00 - 16:30 Afternoon talks :afternoon: @@ -2197,7 +2197,7 @@ execute the buffer, update the talk's info/TALKID.md file. sublicensable to the EmacsConf organizers or that my use of them is fair use. -- in-progress Literate Programming in Emacs Org-Mode :extended:standard:org:tutorial: +- in-progress README-Driven Design :extended:standard:org:tutorial: Name: Adam Ard @@ -2218,7 +2218,7 @@ execute the buffer, update the talk's info/TALKID.md file. exported files and keep your org file to yourself – no one is the wiser. - Watch "Literate Programming in Emacs Org-mode" to learn how you can + Watch "README-Driven Design" 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 @@ -2639,22 +2639,22 @@ execute the buffer, update the talk's info/TALKID.md file. fair use. - + ### 16:30 - 17:00 Closing remarks - + ## NOVEMBER 29 (Sunday) :sun: - + ### 9:00 - 9:10 Opening remarks - + ### 9:10 - 12:00 Morning talks :morning: @@ -3066,12 +3066,12 @@ execute the buffer, update the talk's info/TALKID.md file. TBD - plans for a NonGNU ELPA that will be easy to enable and contribute to without signing copyright assignment papers - + ### 12:00 - 13:00 Lunch - + ### 13:00 - 16:30 Afternoon talks :afternoon: @@ -3835,7 +3835,7 @@ execute the buffer, update the talk's info/TALKID.md file. fair use. - + ### 16:30 - 17:00 Closing remarks @@ -3903,7 +3903,7 @@ fair use. # Code - + ## Planning @@ -4005,7 +4005,7 @@ Some conference-related functions (lambda () (org-entry-get (point) "MIN_TIME")) nil 'tree)))))))) - + ## Generate schedule file diff --git a/2020/submissions.org b/2020/submissions.org index f16057a6..8ddc2f7b 100644 --- a/2020/submissions.org +++ b/2020/submissions.org @@ -1274,7 +1274,7 @@ material owned by third parties, I represent that the material is sublicensable to the EmacsConf organizers or that my use of them is fair use. -**** in-progress Literate Programming in Emacs Org-Mode :extended:standard:org:tutorial: +**** in-progress README-Driven Design :extended:standard:org:tutorial: SCHEDULED: <2020-11-28 Sat 14:18-14:38> :PROPERTIES: :MAX_TIME: 50 @@ -1283,7 +1283,7 @@ SCHEDULED: <2020-11-28 Sat 14:18-14:38> :NAME: Adam Ard :CUSTOM_ID: talk14 :TALK_ID: 14 -:PREREC: planned +:PREREC: done :END: Name: Adam Ard @@ -1305,7 +1305,7 @@ If you are a lone emacs user on your project, simply commit these exported files and keep your org file to yourself -- no one is the wiser. -Watch "Literate Programming in Emacs Org-mode" to learn how you can +Watch "README-Driven Design" 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 -- cgit v1.2.3