diff options
| author | Sacha Chua <sacha@sachachua.com> | 2021-11-13 19:38:45 -0500 |
|---|---|---|
| committer | Sacha Chua <sacha@sachachua.com> | 2021-11-13 19:38:45 -0500 |
| commit | a75f80dd49b7eaa52e40b42ea96aecc33374df6b (patch) | |
| tree | 69b6c32b68fc635d689b01de9f8a3f94404cddd8 /2021 | |
| parent | a9c7cb01b8d0a70c87714e5a5f52862b56408234 (diff) | |
| download | emacsconf-wiki-a75f80dd49b7eaa52e40b42ea96aecc33374df6b.tar.xz emacsconf-wiki-a75f80dd49b7eaa52e40b42ea96aecc33374df6b.zip | |
Mark as captioned
Diffstat (limited to '')
| -rw-r--r-- | 2021/emacsconf-pentabarf.xml | 1621 | ||||
| -rw-r--r-- | 2021/emacsconf.ics | 1128 | ||||
| -rw-r--r-- | 2021/info/model-schedule.md | 2 | ||||
| -rw-r--r-- | 2021/schedule-details.md | 5 |
4 files changed, 163 insertions, 2593 deletions
diff --git a/2021/emacsconf-pentabarf.xml b/2021/emacsconf-pentabarf.xml index 45e959bc..2bb76704 100644 --- a/2021/emacsconf-pentabarf.xml +++ b/2021/emacsconf-pentabarf.xml @@ -1,1620 +1,107 @@ -<schedule><generator name="EmacsConf" version="0.1"></generator><version>20211113120719</version><conference><acronym>emacsconf2021</acronym><title>EmacsConf 2021</title><start>2021-11-27</start><end>2021-11-28</end><time_zone_name>America/Toronto</time_zone_name><base_url>https://emacsconf.org/2021</base_url></conference><day date="2021-11-27" start="2021-11-27T14:00:00Z" end="2021-11-27T22:05:00Z" index="1"><room name="Main"><event id="01" guid="dc07efcd-6d79-cfd4-fed3-59c885fe2922"><date>2021-11-27T14:00:00Z</date><start>09:00</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-day1-open</slug><duration>0:05</duration><title>Opening remarks</title><abstract></abstract><description>Times are approximate and will probably change. +<schedule><generator name="EmacsConf" version="0.1"></generator><version>20211113193833</version><conference><acronym>emacsconf2021</acronym><title>EmacsConf 2021</title><start>2021-11-27</start><end>2021-11-28</end><time_zone_name>America/Toronto</time_zone_name><base_url>https://emacsconf.org/2021</base_url></conference><day date="2021-11-27" start="2021-11-27T14:00:00Z" end="2021-11-27T22:05:00Z" index="1"><room name="Main"><event id="01" guid="dc07efcd-6d79-cfd4-fed3-59c885fe2922"><date>2021-11-27T14:00:00Z</date><start>09:00</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-day1-open</slug><duration>0:05</duration><title>Opening remarks</title><abstract></abstract><description>Times are approximate and will probably change. -# Opening remarks</description><url>https://emacsconf.org/2021/talks/day1-open</url><persons><person>EmacsConf</person></persons></event><event id="02" guid="393ba3c2-b2a6-6a84-44eb-872aa333d08d"><date>2021-11-27T14:05:00Z</date><start>09:05</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-news</slug><duration>0:05</duration><title>Emacs News Highlights</title><abstract></abstract><description>Times are approximate and will probably change. +</description><url>https://emacsconf.org/2021/talks/day1-open</url><persons><person>EmacsConf</person></persons></event><event id="02" guid="393ba3c2-b2a6-6a84-44eb-872aa333d08d"><date>2021-11-27T14:05:00Z</date><start>09:05</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-news</slug><duration>0:05</duration><title>Emacs News Highlights</title><abstract></abstract><description>Times are approximate and will probably change. -# Emacs News Highlights -Sacha Chua <mailto:sacha@sachachua.com> - pronouns: she/her +</description><url>https://emacsconf.org/2021/talks/news</url><persons><person>Sacha Chua</person></persons></event><event id="03" guid="06df8309-bd04-eb24-d443-a780c56adc0a"><date>2021-11-27T14:11:00Z</date><start>09:11</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-frownies</slug><duration>0:20</duration><title>The True Frownies are the Friends We Made Along the Way: An Anecdote of Emacs's Malleability</title><abstract></abstract><description>Times are approximate and will probably change. +</description><url>https://emacsconf.org/2021/talks/frownies</url><persons><person>Case Duckworth</person></persons></event><event id="51" guid="fe959e43-441b-ed34-854b-87f6f481f55a"><date>2021-11-27T14:34:00Z</date><start>09:34</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-pattern</slug><duration>0:24</duration><title>Emacs as Design Pattern Learning</title><abstract></abstract><description>Times are approximate and will probably change. +</description><url>https://emacsconf.org/2021/talks/pattern</url><persons><person>Greta Goetz</person></persons></event><event id="11" guid="ea5bab3c-f31e-68a4-fa23-81ca67fa1990"><date>2021-11-27T15:00:00Z</date><start>10:00</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-unix</slug><duration>0:07</duration><title>GNU's Not UNIX: Why Emacs Demonstrates The UNIX Philosophy Isn't Always The Only Answer</title><abstract></abstract><description>Times are approximate and will probably change. -Quick overview of Emacs community highlights since the last conference +</description><url>https://emacsconf.org/2021/talks/unix</url><persons><person>Daniel Rose</person></persons></event><event id="04" guid="db4ccb28-867f-df24-c073-eaca6edad438"><date>2021-11-27T15:11:00Z</date><start>10:11</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-omegat</slug><duration>0:10</duration><title>Emacs manuals translation and OmegaT</title><abstract></abstract><description>Times are approximate and will probably change. -You can find the links and images at -<https://github.com/sachac/emacsconf-2021-emacs-news-highlights> +</description><url>https://emacsconf.org/2021/talks/omegat</url><persons><person>Jean-Christophe Helary</person></persons></event><event id="05" guid="525d972d-1e34-bcb4-e9c3-861942549357"><date>2021-11-27T15:24:00Z</date><start>10:24</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-nongnu</slug><duration>0:07</duration><title>NonGNU ELPA Update</title><abstract></abstract><description>Times are approximate and will probably change. -Posting the video early to help test formatting. +</description><url>https://emacsconf.org/2021/talks/nongnu</url><persons><person>Philip Kaludercic</person></persons></event><event id="06" guid="245a575a-965a-caa4-8d3b-75f8519c2f3e"><date>2021-11-27T15:36:00Z</date><start>10:36</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-borg</slug><duration>0:08</duration><title>Manual Package Management in The Era of Repositories - Why and How</title><abstract></abstract><description>Times are approximate and will probably change. - +</description><url>https://emacsconf.org/2021/talks/borg</url><persons><person>Dhavan (codingquark)</person></persons></event><event id="07" guid="86158391-53a2-7cb4-d7d3-020afbf6d8d9"><date>2021-11-27T15:48:00Z</date><start>10:48</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-telega</slug><duration>0:08</duration><title>telega.el and the Emacs community on Telegram</title><abstract></abstract><description>Times are approximate and will probably change. -# Questions, answers, and community-provided links +</description><url>https://emacsconf.org/2021/talks/telega</url><persons><person>Gabriele Bozzola</person></persons></event><event id="08" guid="e4bdc2c1-e4b6-67e4-aafb-87ec9aaf846b"><date>2021-11-27T15:58:00Z</date><start>10:58</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-nangulator</slug><duration>0:10</duration><title>Introducing N-Angulator</title><abstract></abstract><description>Times are approximate and will probably change. -<a name="transcript"></a> -# Transcript</description><url>https://emacsconf.org/2021/talks/news</url><persons><person>Sacha Chua</person></persons></event><event id="03" guid="06df8309-bd04-eb24-d443-a780c56adc0a"><date>2021-11-27T14:11:00Z</date><start>09:11</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-frownies</slug><duration>0:20</duration><title>The True Frownies are the Friends We Made Along the Way: An Anecdote of Emacs's Malleability</title><abstract></abstract><description>Times are approximate and will probably change. +</description><url>https://emacsconf.org/2021/talks/nangulator</url><persons><person>Kevin Haddock</person></persons></event><event id="09" guid="14ab7a54-d75d-45e4-85ab-8fd2e391ea41"><date>2021-11-27T16:11:00Z</date><start>11:11</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-janitor</slug><duration>0:26</duration><title>A day in the life of a janitor</title><abstract></abstract><description>Times are approximate and will probably change. -# The True Frownies are the Friends We Made Along the Way: An Anecdote of Emacs's Malleability -Case Duckworth +</description><url>https://emacsconf.org/2021/talks/janitor</url><persons><person>Stefan Monnier</person></persons></event><event id="10" guid="51c360e6-188f-9a34-05bb-0a8d2eb09cdc"><date>2021-11-27T16:42:00Z</date><start>11:42</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-maintainers</slug><duration>0:10</duration><title>How to help Emacs maintainers?</title><abstract></abstract><description>Times are approximate and will probably change. +</description><url>https://emacsconf.org/2021/talks/maintainers</url><persons><person>Bastien Guerry</person></persons></event><event id="12" guid="716d913f-de8b-91a4-5f33-e04ba0905fa5"><date>2021-11-27T16:55:00Z</date><start>11:55</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-gregorian</slug><duration>0:10</duration><title>Typesetting Gregorian Chant with Emacs</title><abstract></abstract><description>Times are approximate and will probably change. +</description><url>https://emacsconf.org/2021/talks/gregorian</url><persons><person>Spencer King</person></persons></event><event id="29" guid="6fccae45-04b5-5524-662b-fdba87754d06"><date>2021-11-27T17:30:00Z</date><start>12:30</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-montessori</slug><duration>0:10</duration><title>Emacs and Montessori Philosophy</title><abstract></abstract><description>Times are approximate and will probably change. -Emacs is well-known for being extremely flexible, programmable, and -extensible; in fact, that's probably the biggest reason it's still -being used after 40+ years of existence, and even has enough clout to -generate an entire conference in its name. In this medium-length -presentation, I will add another point to the data set proving Emacs's -abilities, by narrating the latest package I made, \`frowny.el\`, from -its conception to its current, nearly-completed state. +</description><url>https://emacsconf.org/2021/talks/montessori</url><persons><person>Grant Shangreaux</person></persons></event><event id="52" guid="9cee7e43-bcb1-7f64-c40b-5f9ea938d11a"><date>2021-11-27T17:43:00Z</date><start>12:43</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-erg</slug><duration>0:15</duration><title>Emacs Research Group, Season Zero: What we did together with Emacs in 2 hours a week for a year</title><abstract></abstract><description>Times are approximate and will probably change. -I wrote frowny.el to scratch someone else's itch as a joke on IRC, but -it has been called "pretty useful, for a joke package." I feel like -that encapsulates the spirit of Emacs and that's why I want to present -on this topic. +</description><url>https://emacsconf.org/2021/talks/erg</url><persons><person>Noorah Alhasan</person><person>Joe Corneli</person><person>Raymond Puzio</person><person>Leo Vivier</person></persons></event><event id="13" guid="0f98a5bb-53ce-fb74-1003-0b1f320d414e"><date>2021-11-27T18:01:00Z</date><start>13:01</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-cs</slug><duration>0:10</duration><title>One effective CS grad student workflow</title><abstract></abstract><description>Times are approximate and will probably change. -Along the way, I'll discuss just a little of my own history of Emacs, -and why I feel it's a great tool for non-technical users to sink their -teeth into. +</description><url>https://emacsconf.org/2021/talks/cs</url><persons><person>Greg Coladonato</person></persons></event><event id="16" guid="43cc5db4-e26f-fb44-9aeb-b16c38d8cef3"><date>2021-11-27T18:14:00Z</date><start>13:14</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-professional</slug><duration>0:11</duration><title>Using Org-Mode For Recording Continuous Professional Development</title><abstract></abstract><description>Times are approximate and will probably change. -## Speaker information +</description><url>https://emacsconf.org/2021/talks/professional</url><persons><person>Philip Beadling</person></persons></event><event id="23" guid="a10ce62e-6454-d784-21bb-f6a0488e883c"><date>2021-11-27T18:27:00Z</date><start>13:27</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-tech</slug><duration>0:11</duration><title>Creating technical API documentation and presentations using org-babel, restclient, and org-treeslide</title><abstract></abstract><description>Times are approximate and will probably change. -- Name pronunciation: /keɪs ˈdʌkwə(ɹ)θ/ (CASE DUCK-worth) -- Prounouns: he/him -- Homepage: <https://www.acdw.net> -- Preferred contact info: [email](mailto:acdw@acdw.net) -- Links: - - <https://breadpunk.club>, a shared unix server about bread - - [my Mastodon account](https://writing.exchange/@acdw) (though I'm moving to -[tiny.tilde.website](https://tiny.tilde.website/@acdw) ... soon™)</description><url>https://emacsconf.org/2021/talks/frownies</url><persons><person>Case Duckworth</person></persons></event><event id="51" guid="fe959e43-441b-ed34-854b-87f6f481f55a"><date>2021-11-27T14:34:00Z</date><start>09:34</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-pattern</slug><duration>0:24</duration><title>Emacs as Design Pattern Learning</title><abstract></abstract><description>Times are approximate and will probably change. +</description><url>https://emacsconf.org/2021/talks/tech</url><persons><person>Jan Ypma</person></persons></event><event id="18" guid="b092bc88-e74c-a9c4-611b-d47c99ef578c"><date>2021-11-27T18:40:00Z</date><start>13:40</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-exec</slug><duration>0:08</duration><title>Org as an executable format</title><abstract></abstract><description>Times are approximate and will probably change. -# Emacs as Design Pattern Learning -Greta Goetz +</description><url>https://emacsconf.org/2021/talks/exec</url><persons><person>Tom Gillespie</person></persons></event><event id="17" guid="69763d57-be4e-7e74-509b-92e48a0e7ba6"><date>2021-11-27T18:51:00Z</date><start>13:51</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-org-outside</slug><duration>0:12</duration><title>The use of Org mode syntax outside of GNU/Emacs</title><abstract></abstract><description>Times are approximate and will probably change. +</description><url>https://emacsconf.org/2021/talks/org-outside</url><persons><person>Karl Voit</person></persons></event><event id="22" guid="aed5e190-66a0-3dd4-e5eb-be09be94e6c3"><date>2021-11-27T19:04:00Z</date><start>14:04</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-teach</slug><duration>0:21</duration><title>Using Org-mode to teach programming</title><abstract></abstract><description>Times are approximate and will probably change. +</description><url>https://emacsconf.org/2021/talks/teach</url><persons><person>Daniel German</person></persons></event><event id="20" guid="fd246cee-b5d6-7cc4-2b63-20e87bb7d750"><date>2021-11-27T19:29:00Z</date><start>14:29</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-research</slug><duration>0:05</duration><title>Managing a research workflow (bibliographies, note-taking, and arXiv)</title><abstract></abstract><description>Times are approximate and will probably change. -How do we manage today? This presentation is for people interested in thinking about Emacs as a tool sophisticated enough to cater to the complex assemblage of tasks, people, activities/outcomes, tools (Markauskaite & Goodyear). Some software oversimplifies. Emacs both helps users implement design pattern learning that can cope with complexity while also modeling design pattern learning. By championing the opportunity for users to also be co-creators (cf. Beaty et al.), the free software design at the core and center of Emacs teaches us a way of "being" (Alexander, Gabriel) that can be extended to both the Emacs community and beyond, in a knowledge of how to live (Stiegler, Illich). +</description><url>https://emacsconf.org/2021/talks/research</url><persons><person>Ahmed Khaled</person></persons></event><event id="19" guid="db5821ed-fef4-4934-8fb3-87a0282714de"><date>2021-11-27T19:38:00Z</date><start>14:38</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-babel</slug><duration>0:10</duration><title>Babel for academics</title><abstract></abstract><description>Times are approximate and will probably change. -1. Definition of design patterns and relation to Emacs -2. Why this approach matters -3. Managing complexity: Emacs as mind map -4. Emacs as design pattern framework -5. Personal customization -6. Implementing Emacs as a model for learning -7. Emacs as accommodating complex social, community assemblages +</description><url>https://emacsconf.org/2021/talks/babel</url><persons><person>Asilata Bapat</person></persons></event><event id="21" guid="1fc4917c-aab4-1924-2983-e78f8bca6af9"><date>2021-11-27T19:50:00Z</date><start>14:50</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-molecular</slug><duration>0:11</duration><title>Reproducible molecular graphics with Org-mode</title><abstract></abstract><description>Times are approximate and will probably change. -# References +</description><url>https://emacsconf.org/2021/talks/molecular</url><persons><person>Blaine Mooers</person></persons></event><event id="14" guid="c54c7930-51cc-5184-9dfb-5033e577b95e"><date>2021-11-27T20:03:00Z</date><start>15:03</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-project</slug><duration>0:10</duration><title>Budgeting, Project Monitoring and Invoicing with Org Mode</title><abstract></abstract><description>Times are approximate and will probably change. -- Andler, D. & Guerry, B. (Eds.). *Apprendre demain: Sciences cognitives et éducation à l’ère numérique*, 137-154. Paris: Hatier. -- Alexander, C. (1977). *A pattern language*. New York: Oxford University Press. -- Alexander, C. (1979). *The timeless way of building*. New York: Oxford University Press. -- Alexander, C. (1993). *A foreshadowing of 21st century art: The color and geometry of very early Turkish carpets*. New York: Oxford University Press. -- Beaty, L., Cousin, G., & Hodgson, V. (2010). Revisiting the e-quality in networked learning manifesto. In L. Dirckinck-Holmfeld, V. Hodgson, C. Jones, M. de Laat, D. McConnell, & T. Ryberg (Eds.), *Proceedings of the 7th International Conference on Networked Learning* (pp. 585–592). Aalborg: Lancaster University. http://www.lancs.ac.uk/fss/organisations/netlc/past/nlc2010/abstracts/PDFs/Beaty.pdf. Accessed 30 October 2021. -- Chua, S. (2021). Completing sketches. https://sachachua.com/dotemacs/#org092e0d5. Accessed 29 October 2021. -- Crichton, M. (1983). *Electronic life*. New York: Knopf. -- Gabriel, R. (1996). *Patterns of software*. New York, Oxford: Oxford University Press. -- Goodyear, P. & Retalis, S. (2010). Learning, technology and design. In Goodyear, P. & Retalis, S. (Eds.). *Technology-enhanced learning: Design patterns and pattern languages*, 1-27. Rotterdam, Boston: Sense Publishers. -- Guo, P. (2018). Students, systems, and interactions: Synthesizing the first -four years of Learning@Scale and charting the future. L@S 2018, June 26–28, 2018, London, United Kingdom. DOI: https://doi.org/10.1145/3231644.3231662. <https://pg.ucsd.edu/pubs.htm>. Accessed 25 October 2021. -- Guo, P., Kim, J. & Rubin, R. (2014). How video production affects student engagement: An empirical study of MOOC videos. ACM Conference on Learning at Scale. <https://pg.ucsd.edu/pubs.htm>. Accessed 25 October 2021. -- Illich, I. (1973). *Tools of conviviality*. New York: Harper & Row. -- Kim, J., Guo, P., Seaton, D., Mitros, P., Gajos, K. & Miller, R. (2014). Understanding in-video dropouts and interaction peaks in online lecture videos. ACM Conference on Learning at Scale. <https://pg.ucsd.edu/pubs.htm>. Accessed 25 October 2021. -- Markauskaite, L. & Goodyear, P. (2017). *Epistemic fluency and professional education: innovation, knowledgeable action and actionable knowledge*. Dordrecht: Springer. -- Markel, J. & Guo, P. (2020). Designing the future of experiential learning environments for a post-COVID world: A preliminary case study. NFW ’20 (Symposium on the New Future of Work), August 3–5, 2020, Virtual Event. <https://pg.ucsd.edu/pubs.htm>. Accessed 25 October 2021. -- Morin, E. ([2004] 2008). *La Méthode - tome 6: Éthique*. Éditions du Seuil: Paris. -- Planet Emacs Life. <https://planet.emacslife.com/>. Accessed 25 October 2021 -- Stallman, R. (2002). My Lisp experiences and the development of GNU Emacs. https://www.gnu.org/gnu/rms-lisp.en.html. Accessed 29 October 2021. -- Stiegler, B. (2018). *The neganthropocene*. Open Humanities Press. -- Trocmé-Fabre, H. (1999). *Réinventer le métier d’apprendre*. Paris: Éditions d’organisation. +</description><url>https://emacsconf.org/2021/talks/project</url><persons><person>Adolfo Villafiorita</person></persons></event><event id="15" guid="c9870e10-2600-85a4-24fb-793dfc51164e"><date>2021-11-27T20:16:00Z</date><start>15:16</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-invoice</slug><duration>0:10</duration><title>Finding Your (In)voice: Emacs for Invoicing</title><abstract></abstract><description>Times are approximate and will probably change. +</description><url>https://emacsconf.org/2021/talks/invoice</url><persons><person>Bala Ramadurai</person></persons></event><event id="24" guid="e4e995c0-6e06-8544-a8c3-5f9a06c856fb"><date>2021-11-27T20:29:00Z</date><start>15:29</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-dashboard</slug><duration>0:10</duration><title>Productivity Dashboards with Emacs and Kindle</title><abstract></abstract><description>Times are approximate and will probably change. -# Availability and preferred Q&A approach +</description><url>https://emacsconf.org/2021/talks/dashboard</url><persons><person>Mehmet Tekman</person></persons></event><event id="25" guid="33776e08-e815-db94-971b-a151236e11be"><date>2021-11-27T20:42:00Z</date><start>15:42</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-nyxt</slug><duration>0:10</duration><title>Emacs with Nyxt: extend your editor with the power of a Lisp browser</title><abstract></abstract><description>Times are approximate and will probably change. -Due to the pandemic situation, my teaching schedule fluctuates so I -will not know my availability until much closer to the -date. Therefore, I can only guarantee delayed answer response -(whatever you request), but if available, will join live. -May I please note that I will be pre-recording my video if this submission is accepted. +</description><url>https://emacsconf.org/2021/talks/nyxt</url><persons><person>Andrea</person></persons></event><event id="26" guid="86d4470a-8d19-7bd4-0c53-6aba1b49baef"><date>2021-11-27T20:55:00Z</date><start>15:55</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-design</slug><duration>0:10</duration><title>On the design of text editors</title><abstract></abstract><description>Times are approximate and will probably change. +</description><url>https://emacsconf.org/2021/talks/design</url><persons><person>Nicolas P. Rougier</person></persons></event><event id="53" guid="59e4daca-1e46-9054-9573-9c91966d6987"><date>2021-11-27T21:09:00Z</date><start>16:09</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-dev-update</slug><duration>0:08</duration><title>Emacs development updates</title><abstract></abstract><description>Times are approximate and will probably change. -# Speaker release +</description><url>https://emacsconf.org/2021/talks/dev-update</url><persons><person>John Wiegley</person></persons></event><event id="27" guid="48a8580f-52ce-cc84-6a23-1eddf720ae02"><date>2021-11-27T21:20:00Z</date><start>16:20</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-freedom</slug><duration>0:38</duration><title>How Emacs made me appreciate software freedom</title><abstract></abstract><description>Times are approximate and will probably change. -By submitting this proposal, I agree that my presentation at -EmacsConf 2021 is subject to the following terms and conditions: +</description><url>https://emacsconf.org/2021/talks/freedom</url><persons><person>Protesilaos Stavrou</person></persons></event><event id="28" guid="5287b003-f368-36c4-4f9b-8135734cad39"><date>2021-11-27T22:00:00Z</date><start>17:00</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-day1-close</slug><duration>0:05</duration><title>Closing remarks day 1</title><abstract></abstract><description>Times are approximate and will probably change. -The EmacsConf organizers may capture audio and video (a "Recording") -of my presentation and any associated materials, which may include -slides, notes, transcripts, and prerecording(s) of my presentation -that I provide to the EmacsConf organizers. +</description><url>https://emacsconf.org/2021/talks/day1-close</url><persons><person>EmacsConf</person></persons></event></room></day><day date="2021-11-28" start="2021-11-28T14:00:00Z" end="2021-11-28T22:00:00Z" index="2"><room name="Main"><event id="30" guid="d877a57a-14cf-a194-99c3-a344ecb24acc"><date>2021-11-28T14:00:00Z</date><start>09:00</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-day2-open</slug><duration>0:05</duration><title>Opening remarks day 2</title><abstract></abstract><description>Times are approximate and will probably change. -I authorize the EmacsConf organizers to distribute, reproduce, -publicly display, and prepare derivative works of the Recording and -any derivative works of the Recording (the "Licensed Materials") -under the terms of the Creative Commons Attribution-ShareAlike 4.0 -International (CC BY-SA 4.0) license. +</description><url>https://emacsconf.org/2021/talks/day2-open</url><persons><person>EmacsConf</person></persons></event><event id="31" guid="35d1d9e4-dfdf-f254-6aab-7a466fbfaf09"><date>2021-11-28T14:05:00Z</date><start>09:05</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-faster</slug><duration>0:20</duration><title>How to write faster Emacs Lisp</title><abstract></abstract><description>Times are approximate and will probably change. -I grant to the EmacsConf organizers permission to use my name, -likeness, and biographic information in association with their use -of the Licensed Materials under the above license. +</description><url>https://emacsconf.org/2021/talks/faster</url><persons><person>Dmitry Gutov</person></persons></event><event id="33" guid="599ef3fa-4c73-6c94-4953-75bbc7830681"><date>2021-11-28T14:30:00Z</date><start>09:30</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-structural</slug><duration>0:11</duration><title>Tree-edit: Structural editing for Java, Python, C, and beyond!</title><abstract></abstract><description>Times are approximate and will probably change. -I represent that I have the authority to grant the above license to -the EmacsConf organizers. If my presentation incorporates any -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.</description><url>https://emacsconf.org/2021/talks/pattern</url><persons><person>Greta Goetz</person></persons></event><event id="11" guid="ea5bab3c-f31e-68a4-fa23-81ca67fa1990"><date>2021-11-27T15:00:00Z</date><start>10:00</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-unix</slug><duration>0:07</duration><title>GNU's Not UNIX: Why Emacs Demonstrates The UNIX Philosophy Isn't Always The Only Answer</title><abstract></abstract><description>Times are approximate and will probably change. +</description><url>https://emacsconf.org/2021/talks/structural</url><persons><person>Ethan Leba</person></persons></event><event id="32" guid="29d45a6f-9425-f5a4-bd23-297292e4ab7a"><date>2021-11-28T14:43:00Z</date><start>09:43</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-dsl</slug><duration>0:20</duration><title>Self-Describing Smart DSL's: The Next Magits</title><abstract></abstract><description>Times are approximate and will probably change. -# GNU's Not UNIX: Why Emacs Demonstrates The UNIX Philosophy Isn't Always The Only Answer -Daniel Rose +</description><url>https://emacsconf.org/2021/talks/dsl</url><persons><person>Psionic</person></persons></event><event id="34" guid="8f62e571-91da-bd14-e7c3-b445c7b19d23"><date>2021-11-28T15:06:00Z</date><start>10:06</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-ui</slug><duration>0:10</duration><title>"Yak-shaving to a UI framework" (/"Help! I accidentally yak-shaved my way to writing a UI framework because overlays were slow")</title><abstract></abstract><description>Times are approximate and will probably change. +</description><url>https://emacsconf.org/2021/talks/ui</url><persons><person>Erik Anderson</person></persons></event><event id="35" guid="b073d391-6c37-6bf4-7afb-47edc79631a9"><date>2021-11-28T15:19:00Z</date><start>10:19</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-rust</slug><duration>0:20</duration><title>Extending Emacs in Rust with Dynamic Modules</title><abstract></abstract><description>Times are approximate and will probably change. +</description><url>https://emacsconf.org/2021/talks/rust</url><persons><person>Tuấn-Anh Nguyễn</person></persons></event><event id="38" guid="e7981936-6d72-93d4-8783-5ac64a0ae5bb"><date>2021-11-28T15:44:00Z</date><start>10:44</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-eaf</slug><duration>0:10</duration><title>Emacs Application Framework: A 2021 Update</title><abstract></abstract><description>Times are approximate and will probably change. -The talk targets users who are curious about computational philosophies, -or those who might not know how to best utilise Emacs conceptually. The -talk will cover what the UNIX philosophy is, the GNU Free Software -principles, a typical (Neo)Vi(m) user's approach, and then how one might -accomplish this in Emacs combining the aformentioned ideals. The -listeners will learn how they can approach Emacs ideologically, and how -blocking themselves into one philosophy or the other will limit their -efficiency. Although you may be a veteran GNU/Linux and Emacs user, -understanding how to use both philosophies together will still allow you -to be more performant than without. +</description><url>https://emacsconf.org/2021/talks/eaf</url><persons><person>Matthew Zeng</person></persons></event><event id="47" guid="5e1baaaf-56a3-b5b4-31cb-5437cf465cf9"><date>2021-11-28T15:58:00Z</date><start>10:58</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-model</slug><duration>0:10</duration><title>Extending the "model" of Emacs to other applications</title><abstract></abstract><description>Times are approximate and will probably change. +</description><url>https://emacsconf.org/2021/talks/model</url><persons><person>Laszlo Krajnikovszkij</person></persons></event><event id="50" guid="4cd6de26-cf48-95c4-9d3b-28895a43ec53"><date>2021-11-28T16:11:00Z</date><start>11:11</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-devel</slug><duration>0:20</duration><title>Don't write that package! or: How I learned to stop worrying and love emacs-devel</title><abstract></abstract><description>Times are approximate and will probably change. +</description><url>https://emacsconf.org/2021/talks/devel</url><persons><person>Stefan Kangas</person></persons></event><event id="36" guid="49a35f05-b71f-1d14-2343-a6638bec0d08"><date>2021-11-28T16:36:00Z</date><start>11:36</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-bindat</slug><duration>0:30</duration><title>Turbo Bindat</title><abstract></abstract><description>Times are approximate and will probably change. -# Outline +</description><url>https://emacsconf.org/2021/talks/bindat</url><persons><person>Stefan Monnier</person></persons></event><event id="39" guid="1ddbe380-b4f3-2b84-3cc3-9e799536db8e"><date>2021-11-28T17:40:00Z</date><start>12:40</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-native</slug><duration>0:40</duration><title>Emacs Lisp native compiler, current status and future developments</title><abstract></abstract><description>Times are approximate and will probably change. -- How can one limit their usage of CLI tools while still maintaining - the ideals of both. -- How using CLI tools can still perfectly flow into Emacs. -- How having all programs in Emacs and unified keybindings is akin - to a terminal user. -- Why thinking about computational philosophies might itself be an - impediment.</description><url>https://emacsconf.org/2021/talks/unix</url><persons><person>Daniel Rose</person></persons></event><event id="04" guid="db4ccb28-867f-df24-c073-eaca6edad438"><date>2021-11-27T15:11:00Z</date><start>10:11</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-omegat</slug><duration>0:10</duration><title>Emacs manuals translation and OmegaT</title><abstract></abstract><description>Times are approximate and will probably change. +</description><url>https://emacsconf.org/2021/talks/native</url><persons><person>Andrea Corallo</person></persons></event><event id="40" guid="5947c3e9-93c1-1014-7ffb-aa0e0097e3e4"><date>2021-11-28T18:27:00Z</date><start>13:27</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-form</slug><duration>0:10</duration><title>Old McCarthy Had a Form</title><abstract></abstract><description>Times are approximate and will probably change. -# Emacs manuals translation and OmegaT -Jean-Christophe Helary +</description><url>https://emacsconf.org/2021/talks/form</url><persons><person>Ian Eure</person></persons></event><event id="37" guid="5e162d34-ea19-8544-b693-dd6da0e885cd"><date>2021-11-28T18:41:00Z</date><start>13:41</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-test</slug><duration>0:05</duration><title>Test blocks</title><abstract></abstract><description>Times are approximate and will probably change. +</description><url>https://emacsconf.org/2021/talks/test</url><persons><person>Eduardo Ochs</person></persons></event><event id="41" guid="51023225-018f-cf24-9d73-3c267907c13e"><date>2021-11-28T18:49:00Z</date><start>13:49</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-bug</slug><duration>0:20</duration><title>Let's talk about bug trackers</title><abstract></abstract><description>Times are approximate and will probably change. +</description><url>https://emacsconf.org/2021/talks/bug</url><persons><person>Bastien Guerry</person></persons></event><event id="42" guid="1407591a-29fd-3f64-1beb-01dea6e9d7d2"><date>2021-11-28T19:16:00Z</date><start>14:16</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-bidi</slug><duration>0:20</duration><title>Perso-Arabic Input Methods And Making More Emacs Apps BIDI Aware</title><abstract></abstract><description>Times are approximate and will probably change. -Even if it is generally agreed that software localization is a good thing, Emacs is lacking in that respect for a number of technical reasons. Nonetheless, the free software using public could greatly benefit from Emacs manuals translations, even if the interface were to remain in English. +</description><url>https://emacsconf.org/2021/talks/bidi</url><persons><person>Mohsen BANAN</person></persons></event><event id="43" guid="3364aedb-a496-5c64-5383-b0080afa6d7b"><date>2021-11-28T19:41:00Z</date><start>14:41</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-mold</slug><duration>0:10</duration><title>Moldable Emacs, a step towards sustainable software</title><abstract></abstract><description>Times are approximate and will probably change. -OmegaT is a multiplatform GPL3+ "computer aided translation" (CAT) tool running on OpenJDK 8. CATs are roughly equivalent for translators to what IDEs are for code writers. Casual translators can benefit from their features but professionals or committed amateurs are the most likely to make the most use of such tools. +</description><url>https://emacsconf.org/2021/talks/mold</url><persons><person>Andrea</person></persons></event><event id="44" guid="daf3570b-3df3-9db4-a1f3-ce98d9863717"><date>2021-11-28T19:55:00Z</date><start>14:55</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-clede</slug><duration>0:20</duration><title>CLEDE the Common Lisp Emacs Development Environment.</title><abstract></abstract><description>Times are approximate and will probably change. -When OmegaT, free software based forges and Emacs meet, we have a free multi-user translation environment that can easily sustain the (close to) 2 million words load that comprise the manuals distributed with Emacs, along with powerful features like arbitrary string protection for easy typing and QA (quality assurance), automatic legacy translation handling, glossary management, history based or predictive autocompletion, etc. +</description><url>https://emacsconf.org/2021/talks/clede</url><persons><person>Fermin MF</person></persons></event><event id="45" guid="f03ae971-4d2b-ccc4-2643-4ae2391ce1ab"><date>2021-11-28T20:22:00Z</date><start>15:22</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-imaginary</slug><duration>0:11</duration><title>Imaginary Programming</title><abstract></abstract><description>Times are approximate and will probably change. -The current trial project for French is hosted on 2 different forges: +</description><url>https://emacsconf.org/2021/talks/imaginary</url><persons><person>Shane Mulligan</person></persons></event><event id="46" guid="27595637-b6b9-f764-805b-ff1b7f009006"><date>2021-11-28T20:36:00Z</date><start>15:36</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-build</slug><duration>0:20</duration><title>How to build an Emacs</title><abstract></abstract><description>Times are approximate and will probably change. -1. sr.ht hosts the source files - <https://sr.ht/~brandelune/documentation_emacs/> -2. chapril hosts the OmegaT team project architecture - <https://forge.chapril.org/brandelune/documentation_emacs> +</description><url>https://emacsconf.org/2021/talks/build</url><persons><person>Fermin MF</person></persons></event><event id="48" guid="80d1ad02-5fe4-03b4-c573-17ea6cdb61aa"><date>2021-11-28T21:03:00Z</date><start>16:03</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-forever</slug><duration>0:40</duration><title>M-x Forever: Why Emacs will outlast text editor trends</title><abstract></abstract><description>Times are approximate and will probably change. -The sources are regularly updated with a po4a based shell script. +</description><url>https://emacsconf.org/2021/talks/forever</url><persons><person>David Wilson (System Crafters)</person></persons></event><event id="49" guid="828e7c62-8430-f1a4-431b-63c308d58688"><date>2021-11-28T21:50:00Z</date><start>16:50</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-day2-close</slug><duration>0:10</duration><title>Closing remarks day 2</title><abstract></abstract><description>Times are approximate and will probably change. -# Outline - -- Duration: 10 minutes -- Software used during the presentation - - [po4a](https://po4a.org) a tool to convert documentation formats to and from the commonly used `gettext` **PO** format. - po4a supports the `texinfo` format along with many others. - - [OmegaT](https://omegat.org) a "computer aided translation" tool used by translators to efficiently combine translation resources (legacy translations, glossaries, etc.) so as to produce more consistent translations. - -During this short presentation, I will address: - -- The specificities of the Emacs manuals and the difficulties they present to the translator -- The reason why a professional tool is better than a collaborative web-based system -- How to convert the texi and org files to a format that translators can handle -- How to adapt OmegaT to the Emacs manual specificities -- How to use OmegaT features such as arbitrary string protection, legacy translation handling, glossaries, autocompletion, QA, etc. -- How to use OmegaT with a team of 2 (or more) translators working at the same time - - -I will *not* show: - -- How to create an OmegaT project -- How to set up an OmegaT team project -- How to use OmegaT from the command line to work in localization pipelines -- How to use machine translation and MT "post-edit" -- How to convert back the translated files to texi format -- How to install translated texi files for use in Emacs - -People who are interested in knowing more about OmegaT are invited to check the [online user manual](https://omegat.sourceforge.io/manual-latest/en/). - -# Personal information -- Name pronunciation: [ʒɑ̃kRstɔf elaRi](https://doublet.jp/wp-content/uploads/2021/11/jch.ogg) -- Pronouns: he -- Homepage: [https://mac4translators.blogspot.com](https://mac4translators.blogspot.com) -- Preferred contact info: [jean.christophe.helary@traduction-libre.org](jean.christophe.helary@traduction-libre.org) -- Links for sponsoring/supporting (multilingual translations): [https://doublet.jp](https://doublet.jp)</description><url>https://emacsconf.org/2021/talks/omegat</url><persons><person>Jean-Christophe Helary</person></persons></event><event id="05" guid="525d972d-1e34-bcb4-e9c3-861942549357"><date>2021-11-27T15:24:00Z</date><start>10:24</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-nongnu</slug><duration>0:07</duration><title>NonGNU ELPA Update</title><abstract></abstract><description>Times are approximate and will probably change. - -# NonGNU ELPA Update -Philip Kaludercic - - - -NonGNU ELPA was announced last year, as a package repository -that will be enabled by default in Emacs, but doesn't require -any copyright assignment. This means that a lot of popular -packages can now be installed easier, without any additional -configuration. - -In this talk I would like the give a reminder of what NonGNU -ELPA is and how it works, update the participants on what has -happened since last year and what maintainers have to do if they -want their packages to be added to the repository.</description><url>https://emacsconf.org/2021/talks/nongnu</url><persons><person>Philip Kaludercic</person></persons></event><event id="06" guid="245a575a-965a-caa4-8d3b-75f8519c2f3e"><date>2021-11-27T15:36:00Z</date><start>10:36</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-borg</slug><duration>0:08</duration><title>Manual Package Management in The Era of Repositories - Why and How</title><abstract></abstract><description>Times are approximate and will probably change. - -# Manual Package Management in The Era of Repositories - Why and How -Dhavan (codingquark) - - - -Emacs now has many package repositories - enought to have conflicts -and arguments about. The packages are becoming big, they depend on many -other packages and it is not easy to keep track of what all is being -installed in our Emacsen. An aggressive way out of this is to use Yet -Another Package and install all elisp code manually - with borg[1]. - -[1]: <https://github.com/emacscollective/borg> - - - -# Outline - -- 5-10 minutes: (brief description/outline) - 1. What are we trying to solve? - 2. What is borg? - 3. How to use it? - 4. Assimilate a package for demo</description><url>https://emacsconf.org/2021/talks/borg</url><persons><person>Dhavan (codingquark)</person></persons></event><event id="07" guid="86158391-53a2-7cb4-d7d3-020afbf6d8d9"><date>2021-11-27T15:48:00Z</date><start>10:48</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-telega</slug><duration>0:08</duration><title>telega.el and the Emacs community on Telegram</title><abstract></abstract><description>Times are approximate and will probably change. - -# telega.el and the Emacs community on Telegram -Gabriele Bozzola and Evgeny Zajcev - - - -Telegram is a cross-platform instant messaging system. The large number of -features and the widespread adoption make it a good choice for both private -conversations with friends and for large online communities. In this talk, I -am going to present the Emacs community on Telegram and its initiatives. I -am also going to discuss telega.el, the Emacs client for Telegram. telega.el -is a high-quality package that perfectly integrates in Emacs. It supports -the vast majority of the features supported by the official clients, while -adding several unique ones. In the talk, I will present the package and -highlight some of the most important features.</description><url>https://emacsconf.org/2021/talks/telega</url><persons><person>Gabriele Bozzola</person></persons></event><event id="08" guid="e4bdc2c1-e4b6-67e4-aafb-87ec9aaf846b"><date>2021-11-27T15:58:00Z</date><start>10:58</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-nangulator</slug><duration>0:10</duration><title>Introducing N-Angulator</title><abstract></abstract><description>Times are approximate and will probably change. - -# Introducing N-Angulator -Kevin Haddock - - - -The Unix file system is essentially an N-dimentional sparse array that -currently lacks a decent editor and browser which -can effectively leverage the logical tri-angulation (or, more properly -"n-angulation") of atoms/blobs within it. - -N-Angulator is the genesis, to wit, the "Model-T," of such a program. - -(see google drive link below for a very old uncirculated prototype -video demo. Be sure and turn the volume UP!) - -na.intro.flv -<https://drive.google.com/file/d/1EZN0Xs8eGlEbSIYFml2lp3GCNnmLQa98/view?usp=drive_web> - - - -# Outline - -- 5-10 minutes: (brief description/outline) - -The reconceptualization of the Unix file system as the N-Dimensional -sparse array will be discussed. - -A simple pre-existing database will be queried. - -If time, questions will be entertained by video/audio and/or IRC.</description><url>https://emacsconf.org/2021/talks/nangulator</url><persons><person>Kevin Haddock</person></persons></event><event id="09" guid="14ab7a54-d75d-45e4-85ab-8fd2e391ea41"><date>2021-11-27T16:11:00Z</date><start>11:11</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-janitor</slug><duration>0:26</duration><title>A day in the life of a janitor</title><abstract></abstract><description>Times are approximate and will probably change. - -# A day in the life of a janitor -Stefan Monnier - - - -Because of a reckless former Emacs maintainer that shall - better stay unnamed, ELisp has seen a fair bit of churn in the last 10 - years, making it necessary to clean up "old" code [in order to open up - the road for yet more recklessness? ]. - In this documentary we will follow a famous janitor in his every day job - dealing with the aftermath of the cl-lib / lexical-binding party. - -- ~20 minutes - Here really, I'm not sure how much time this will take. I put 20 - minutes because I think I might be able to fill that and I think more - than that could turn too boring. I intend to make it a "live coding" - kind of thing, without anything like an outline: it's basically "make" - followed by fixing the warnings.</description><url>https://emacsconf.org/2021/talks/janitor</url><persons><person>Stefan Monnier</person></persons></event><event id="10" guid="51c360e6-188f-9a34-05bb-0a8d2eb09cdc"><date>2021-11-27T16:42:00Z</date><start>11:42</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-maintainers</slug><duration>0:10</duration><title>How to help Emacs maintainers?</title><abstract></abstract><description>Times are approximate and will probably change. - -# How to help Emacs maintainers? -Bastien Guerry - - - -After 11 years of helping as the Org maintainer, I would -like to share a few lessons learned. My goal is help everyone take -care of Emacs maintainance by taking care of Emacs maintainers. - - - -# Outline - -- 5-10 minutes</description><url>https://emacsconf.org/2021/talks/maintainers</url><persons><person>Bastien Guerry</person></persons></event><event id="12" guid="716d913f-de8b-91a4-5f33-e04ba0905fa5"><date>2021-11-27T16:55:00Z</date><start>11:55</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-gregorian</slug><duration>0:10</duration><title>Typesetting Gregorian Chant with Emacs</title><abstract></abstract><description>Times are approximate and will probably change. - -# Typesetting Gregorian Chant with Emacs -Spencer King - - - -There are a variety of methods for typesetting gregorian -chant scores and outputting high-quality sheet music. One of these is -a tool called Gregorio, which integrates with LaTeX allowing scores to -be cleanly inserted into other documents. All Gregorio files are plain -text, allowing them to easily be shared with other users and managed -with a version control system. In this talk, I will give a brief -overview of the Gregorio tool and then show how it can be used in -Emacs by typesetting a simple score. All code and examples will be -made available to help new users get started with typesetting their -own scores. - - - -# Outline - -- 5-10 minutes: (brief description/outline) - 1. Introduction to chant music - 2. Introduction to Gregorio - 3. Example of typesetting a score in Emacs - 4. Code and example availability</description><url>https://emacsconf.org/2021/talks/gregorian</url><persons><person>Spencer King</person></persons></event><event id="29" guid="6fccae45-04b5-5524-662b-fdba87754d06"><date>2021-11-27T17:30:00Z</date><start>12:30</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-montessori</slug><duration>0:10</duration><title>Emacs and Montessori Philosophy</title><abstract></abstract><description>Times are approximate and will probably change. - -# Emacs and Montessori Philosophy - - - - -As a former Montessori guide and now parent, I often think about the -relationship of this particular educational philosophy and how it manifests -in my work with software, Emacs in particular. This talk introduces the -concept of Emacs as an educational environment and how it expresses elements of -Montessori psychology regarding "Human Tendencies". Human tendencies are innate -drives present in everybody that allow us to explore and make sense of our world. - - - -# Outline - -- 5-10 minutes: (brief description/outline) - Quick overview of a Montessori classroom environment: - - - the adults or guides primarily observe and present material - - the children are free to explore materials as they choose (within limits) - - the environment itself is prepared specifically to foster engagement - - Enumerate the "Human Tendencies": - - - Abstraction - - Activity - - Communication - - Exactness - - Exploration - - Manipulation (of the environment) - - Order - - Orientation - - Repetition - - Self-Perfection - - Work (also described as "purposeful activity") - - How does Emacs express these things? - - - in the short version, pose the question, and perhaps give one example. - - Emacs is an environment that provides facilities for individuals to - find their way to proficiency through their Human Tendencies. - - We are all both learners and guides, Emacs is our classroom</description><url>https://emacsconf.org/2021/talks/montessori</url><persons><person>Grant Shangreaux</person></persons></event><event id="52" guid="9cee7e43-bcb1-7f64-c40b-5f9ea938d11a"><date>2021-11-27T17:43:00Z</date><start>12:43</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-erg</slug><duration>0:15</duration><title>Emacs Research Group, Season Zero: What we did together with Emacs in 2 hours a week for a year</title><abstract></abstract><description>Times are approximate and will probably change. - -# Emacs Research Group, Season Zero: What we did together with Emacs in 2 hours a week for a year -Noorah Alhasan, Joe Corneli, Raymond Puzio, Leo Vivier - - - -The four of us met at EmacsConf 2020, and joined together around a -common interest in Emacs and research. Since then, we have convened as -the Emacs Research Group for weekly meetings. During these meetings, we -took notes collaboratively, using a ‘conflict-free replicated data type’ -package (crdt.el); at the end of each session, we debriefed using a -template that we call a Project Action Review (PAR). As as a -meta-review of our sessions, every six weeks we prepared a Causal -Layered Analysis (CLA), which gave us a different perspective on what we -had done. We reflected further on our experiences and methods, linking -our CLA to plans and design patterns. As a formal research output, we -contributed a write-up of these matters to a joint paper which we -presented at the Pattern Languages of Programs Conference (PLoP 2021). -The paper included an interactive workshop, in which we explored roles -in real-time problem solving and collaboration. - -In our short talk we share information about these methods, making a -case for other people getting together and creating their own small -research communities similar to ours.</description><url>https://emacsconf.org/2021/talks/erg</url><persons><person>Noorah Alhasan</person><person>Joe Corneli</person><person>Raymond Puzio</person><person>Leo Vivier</person></persons></event><event id="13" guid="0f98a5bb-53ce-fb74-1003-0b1f320d414e"><date>2021-11-27T18:01:00Z</date><start>13:01</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-cs</slug><duration>0:10</duration><title>One effective CS grad student workflow</title><abstract></abstract><description>Times are approximate and will probably change. - -# One effective CS grad student workflow -Greg Coladonato - - - -When I was an undergrad, I learned many things, most of -which I forgot. In the time since then, I've discovered Org Mode, Org -Roam, Org Noter, Org Ref. PDF Tools, and Anki. I would like to share -my approach for capturing all the information that comes my way as a -MS CS student at Georgia Tech, in the hopes that I can both get -feedback on ways to improve the system I use, as well as hopefully -inspire others to build workflows that make them more productive. - - - -# Outline - -- 5-10 minutes: Go through some typical workflows associated with being a grad student, using the packages mentioned in the abstract.</description><url>https://emacsconf.org/2021/talks/cs</url><persons><person>Greg Coladonato</person></persons></event><event id="16" guid="43cc5db4-e26f-fb44-9aeb-b16c38d8cef3"><date>2021-11-27T18:14:00Z</date><start>13:14</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-professional</slug><duration>0:11</duration><title>Using Org-Mode For Recording Continuous Professional Development</title><abstract></abstract><description>Times are approximate and will probably change. - -# Using Org-Mode For Recording Continuous Professional Development -Philip Beadling - - - -I recently had the pleasure of being audited for my CPD record with one -of the large engineering professional bodies. I decided to harness -org-mode's TODO lists to record CPD items and my progress against them -completely within Emacs. I also wanted the ability to export the data -in a well presented, compact format for auditing submission. - -The project was a success (I passed the audit) and the resulting system -integrates really well into my wider daily Emacs workflow, making future -CPD recording seamless. - -The talk will explain how I tweaked and extended org-mode to get it to -record the data I wanted, followed by a demo. - -A basic demo org file with embedded elisp can be seen here: -<https://raw.githubusercontent.com/falloutphil/Misc/master/cpd.org> - -A basic generated PDF from the basic demo is here: - - -I have a much more involved example I could also use for the demo. - -The template contains a few examples. Examples are Goals that are split -up into Activities. All Activities must have a Goal, and within a Goal -all activities must be complete for the Goal to be automatically set to -complete. - -It's basically leveraging Org Capture Templates to create custom Goals -and Activities. - -On save or update these are then rendered into a table using Column View. - -Activities are sorted by date they were completed on. - -The Column View is pre-configured to be exported to PDF in a condensed -but readable format for submission. It stays fairly readable even when -the pages get busy. - -The elisp required is all under the "Config" bullet and Emacs will ask -to execute it on opening the Org file. The elisp concerns itself with -nice custom org capture functions and a few functions to ensure nice -formatting on export, etc. - - - -# Outline - -- 5-10 minutes: - -A quick walkthrough of the setup and functions, followed by a demo of how -to add CPD items, and update them. Finally show generation of a PDF -containing all the items tabulated and ready for audit review. I -estimate this at approx 10 minutes.</description><url>https://emacsconf.org/2021/talks/professional</url><persons><person>Philip Beadling</person></persons></event><event id="23" guid="a10ce62e-6454-d784-21bb-f6a0488e883c"><date>2021-11-27T18:27:00Z</date><start>13:27</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-tech</slug><duration>0:11</duration><title>Creating technical API documentation and presentations using org-babel, restclient, and org-treeslide</title><abstract></abstract><description>Times are approximate and will probably change. - -# Creating technical API documentation and presentations using org-babel, restclient, and org-treeslide -Jan Ypma - - - -The emacs org-babel package is often mentioned in conjunction with -literate programming. The ability to mix code segments with prose -indeed offers an intuitive way to augment semantic code pieces with -textual descriptions. - -In recent projects, I've started to turn to org-mode as the primary -format to maintain technical documentation, as well as slides for a -technical language course. By using org-babel to pull in "live" code -for REST requests, language examples, and shell scripts, one can be -sure that the documentation and slides are never out of date. - -The session will show how leverage org-babel, restclient and -org-treeslide to write and present technical documentation with style. - - -# Outline - -- Introduction -- Demo: Developer guide -- Demo: REST API guide -- Demo: Presentations -- Used packages and configuration</description><url>https://emacsconf.org/2021/talks/tech</url><persons><person>Jan Ypma</person></persons></event><event id="18" guid="b092bc88-e74c-a9c4-611b-d47c99ef578c"><date>2021-11-27T18:40:00Z</date><start>13:40</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-exec</slug><duration>0:08</duration><title>Org as an executable format</title><abstract></abstract><description>Times are approximate and will probably change. - -# Org as an executable format -Tom Gillespie - - - -Org mode is known for its flexibility, power, and staggeringly diverse -number of workflows, users, and use cases. - -This talk explores just how far we can push the boundaries of the sane -and sensible with regard to Org workflows. - -In particular it will discuss shebang blocks, and elvs: two parts of a -complete system for creating executable Org files. - -Org syntax does not support shebang lines. However, it turns out that -Org syntax enables something even better &#x2014; shebang blocks. - -Org is also (supposedly) not an executable file format. However, by -combining a shebang block with a Org babel source block, and eval -local variables (elvs) Org becomes a multi-language executable format. - -In this talk we introduce shebang blocks and elvs as a two part system -that transforms Org files into executable documents that can run on any -recent version of Emacs. - -These ideas are implemented in -<https://github.com/tgbugs/orgstrap/blob/master/README.org> and -<https://github.com/tgbugs/orgstrap/blob/master/shebang.org>, and -orgstrap.el is available as a package on MELPA and can be installed -via M-x install-package orgstrap. - -The talk will open with a demo of how to create an executable Org file -using the orgstrap machinery. - -We then discuss security considerations, and show example use cases. - -Finally the talk will cover the details and development of the -portable shebang block for Org mode that works on a wide variety of -systems and shells, and on the development of a formal specification -and a reference implementation for using Org source blocks to -transform Org files from plain text documents with a bit of markup -into self describing computational documents, or interactive -applications. - - - -# Outline - -- 5-10 minutes: - -A demo of adding the orgstrap block and elvs, -adding a shebang block, and then running an org file.</description><url>https://emacsconf.org/2021/talks/exec</url><persons><person>Tom Gillespie</person></persons></event><event id="17" guid="69763d57-be4e-7e74-509b-92e48a0e7ba6"><date>2021-11-27T18:51:00Z</date><start>13:51</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-org-outside</slug><duration>0:12</duration><title>The use of Org mode syntax outside of GNU/Emacs</title><abstract></abstract><description>Times are approximate and will probably change. - -# The use of Org mode syntax outside of GNU/Emacs -Karl Voit - - - -With the rising interest in Org mode, the GNU/Emacs community gained -much momentum in the last decade. Being a nicely designed lightweight -markup language, Org mode does not only benefit users of GNU/Emacs. -There are many tools and services supporting Org mode syntax documents -that do have no direct connection to GNU/Emacs. I would like to -elaborate on the advantages on using Org mode syntax for arbitrary -text outside of GNU/Emacs for better typing usability and -collaboration tasks. - - - -# Outline - -- 5-10 minutes: (brief description/outline) - -This can only be a short teaser for the use of Org mode syntax without -much comparison to other lightweight markup languages. For this -audience, I do think that this would be too short because most -attendees might already have heard the rumors that Org mode is great -or they have adapted Org mode in their workflows already.</description><url>https://emacsconf.org/2021/talks/org-outside</url><persons><person>Karl Voit</person></persons></event><event id="22" guid="aed5e190-66a0-3dd4-e5eb-be09be94e6c3"><date>2021-11-27T19:04:00Z</date><start>14:04</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-teach</slug><duration>0:21</duration><title>Using Org-mode to teach programming</title><abstract></abstract><description>Times are approximate and will probably change. - -# Using Org-mode to teach programming -Daniel German - - - -In this presentation I will explain how to use org-mode effectively to -prepare teaching materials, and how to present them. - -For the last 5 years I have been using org-mode to teach programming -in different languages: C++, SQL, Ruby, Python, SML -and Scheme. Org-mode has three key advantages: - -1. it supports most programming languages with a common interface, -2. it is an interactive medium for delivering teaching materials; and -3. it is an always-up-to-date format that does not need to be exported in order to be published. - -I explain how I use org-mode in my courses and how I combine org-mode -notes other tools such as github org-mode to get -always up-to-date teaching materials that one can use for both -teaching and studying (see -<https://github.com/dmgerman/csc116ModernCplusplus/blob/master/lectures/l-01-1-intro/01_1_intro.org> -for an example). - -Finally, I will discuss some important aspects to consider when using -org-mode for this purpose. - - - -# Outline - -20 minutes: - -- Introduction -- Quick demonstration -- Workflow -- Some Important considerations -- Emacs configuration and how to get started - -I have create a git repository with examples and config files that is ready to use: -<https://github.com/dmgerman/teachingProgOrg></description><url>https://emacsconf.org/2021/talks/teach</url><persons><person>Daniel German</person></persons></event><event id="20" guid="fd246cee-b5d6-7cc4-2b63-20e87bb7d750"><date>2021-11-27T19:29:00Z</date><start>14:29</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-research</slug><duration>0:05</duration><title>Managing a research workflow (bibliographies, note-taking, and arXiv)</title><abstract></abstract><description>Times are approximate and will probably change. - -# Managing a research workflow (bibliographies, note-taking, and arXiv) -Ahmed Khaled - - - -Researchers and knowledge workers have to read and discover new papers, -ask questions about what they read, write notes and scratchwork, and store -much of this information for use in writing papers and/or code. Emacs allows -us to do all of this (and more) using simple text interfaces that integrate -well together. In this talk I will talk about the following: - -a. Using elfeed and elfeed-score to read new papers from arXiv. -b. Using org-ref to import arXiv papers of interest into a local -bibliography. -c. Using Emacs hooks with biber and rebiber in order to keep the local - bibliography clean and up-to-date with conference versions of papers. -d. Using org-roam and org-roam-bibtex to take linked, searchable notes in -org on research papers. - -This text-based workflow allows for keeping everything accessible under -version -control and avoids the platform lock-in of binary formats (e.g. Mendeley). I -will share my Doom Emacs configuration for this workflow, but it is not -limited -to Doom. - - - -# Outline - -- 5-10 minutes: I will demo the packages I use in 5 minutes.</description><url>https://emacsconf.org/2021/talks/research</url><persons><person>Ahmed Khaled</person></persons></event><event id="19" guid="db5821ed-fef4-4934-8fb3-87a0282714de"><date>2021-11-27T19:38:00Z</date><start>14:38</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-babel</slug><duration>0:10</duration><title>Babel for academics</title><abstract></abstract><description>Times are approximate and will probably change. - -# Babel for academics -Asilata Bapat - - - -Plain org-mode is already an extremely powerful and -customisable tool for task and time management, note-taking, calendar -and agenda management, and much more. Babel takes org a step further -by letting you write, evaluate, and export code in different languages -from within a single file. In this talk, I will highlight some -features of babel that I find exciting and extremely useful, -particularly for an academic workflow. - -Getting started with babel can be intimidating, but it's hard to stop -using it once you start. As an academic, I typically don't manage -large coding projects. My primary purpose is writing lecture notes, -assignments, and papers, and managing related admin. Typically, I want -to try and automate the boring portions of my workflow without extra -overhead. I also tend to find various tasks easier in some programming -languages and harder in others, and prefer to mix and match languages -as the task dictates. Babel makes this process seamless. - -A basic use case is writing a document in org-mode and exporting it to -LaTeX or HTML. Org-mode even lets you write multiple documents in a -single org file, which can be convenient. Babel lets you add all sorts -of enhancements to the same file. For example, suppose we have a -single org document with all the problem sets for a course. Within -this single file, we could now: - -- draw pictures in ditaa, graphviz, or python instead of LaTeX, -- use python to do complex calculations and then output the result as LaTeX, -- define skeletons to quickly draw up assignment templates, -- toggle exporting of assignments with or without solutions based on tags, -- locally change export settings or run a post-export hook, -- automatically export to LaTeX after saving, -- tangle code blocks from some or all of the languages to external files. - -I will try to showcase features of babel that academics could find -helpful, by presenting some ways in which I have tried to use babel. I -would also like to be inspired by other people's babel workflows! - - - -# Outline - -- 5-10 minutes: (brief description/outline) - -For a 5-10 minute presentation I will give a brief intro and present one or two example files that heavily use babel. I will use these -examples to highlight some of the features mentioned in the abstract.</description><url>https://emacsconf.org/2021/talks/babel</url><persons><person>Asilata Bapat</person></persons></event><event id="21" guid="1fc4917c-aab4-1924-2983-e78f8bca6af9"><date>2021-11-27T19:50:00Z</date><start>14:50</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-molecular</slug><duration>0:11</duration><title>Reproducible molecular graphics with Org-mode</title><abstract></abstract><description>Times are approximate and will probably change. - -# Reproducible molecular graphics with Org-mode -Blaine Mooers - - - -Research papers in structural biology should include the code used to make -the images of molecules in the article in the supplemental materials. -Some structural bioinformaticists have started to include -their computer code in the supplemental materials to allow readers -to reproduce their analyses. However, authors of papers reporting new -molecular structures often overlook the inclusion of the code that makes -the images of the molecules reported in their articles. Nonetheless, -this aspect of reproducible research needs to become the standard practice -to improve the rigor of the science. - -In a literate programming document, the author interleaves blocks -of explanatory prose between code blocks that make the images of molecules. -The document allows the reader to reproduce the images in the manuscript by running the code. -The reader can also explore the effect of altering the parameters in the -code. Org files are one alternative for making such literate programming -documents. - -We developed a **yasnippet** snippet library called **orgpymolpysnips** for -structural biologists (<https://github.com/MooersLab/orgpymolpysnips>). -This library facilitates the assembly of literate programming documents -with molecular images made by PyMOL. PyMOL is the most popular -molecular graphics program for creating images for publication; it has -over 100,000 users, which is a lot of users in molecular biology. PyMOL -has been used to make many of the images of biological molecules found -on the covers of many Cell, Nature, and Science issues. - -We used the **jupyter** language in **org-babel** to send commands from -code blocks in Org files to PyMOL's Python API. PyMOL returns the -molecular image to the output block below the code block. An Emacs -user can convert the Org file into a PDF, `tangle' the code blocks -into a script file, and submit these for non-Emacs users. We describe -the content of the library and provide examples of the running PyMOL -from Org-mode documents. - - -# Outline - -- 5-10 minutes: (brief description/outline) - - Title slide - - Structural Biolog Workflow in the Mooers Lab - - Cover images made with PyMOL - - - Why develop a snippet library for your field? - - PyMOL in Org: kernel specification - - Creating a conda env and installing PyMOL - - Example code block in Org to make DSSR block model of tRNA - - Resulting image - - Summary - - Acknowledgements</description><url>https://emacsconf.org/2021/talks/molecular</url><persons><person>Blaine Mooers</person></persons></event><event id="14" guid="c54c7930-51cc-5184-9dfb-5033e577b95e"><date>2021-11-27T20:03:00Z</date><start>15:03</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-project</slug><duration>0:10</duration><title>Budgeting, Project Monitoring and Invoicing with Org Mode</title><abstract></abstract><description>Times are approximate and will probably change. - -# Budgeting, Project Monitoring and Invoicing with Org Mode -Adolfo Villafiorita - - - -In this talk I will present how we use Org Mode at Shair.Tech for -budgeting, project monitoring, and invoicing. - -We are a small company and we are still tuning and improving the -process, but with a bit of Emacs Lisp, the functions Org Mode -provides, and reading here and there what other users do, we -implemented an effective workflow we have been using for nearly a -year, now, and with which we are very happy. Talk duration: - -&#x2013;> 20 minutes seems to be right (15 talk + questions) -&#x2013;> I can also make in 10 minutes, by focusing the talk on - budgeting (or monitoring)</description><url>https://emacsconf.org/2021/talks/project</url><persons><person>Adolfo Villafiorita</person></persons></event><event id="15" guid="c9870e10-2600-85a4-24fb-793dfc51164e"><date>2021-11-27T20:16:00Z</date><start>15:16</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-invoice</slug><duration>0:10</duration><title>Finding Your (In)voice: Emacs for Invoicing</title><abstract></abstract><description>Times are approximate and will probably change. - -# Find Your (In)voice: Emacs for Invoicing -Bala Ramadurai - - - -Ye Freelance warriors, please lend me your I/O devices for 5 minutes. - -Your time is your money! Do you find it a pain to generate an invoice, -record the details into your accounting software and keep track of -taxes and payments? You are not alone, I found the whole invoice -thingy to be extremely painful. - -But worry not, Emacs comes to our rescue. - -My talk will give you a basic intro on how to use org mode, some embedded python code and file jugglery to generate stylistic and professional invoices. - -What you will learn during the session: - -- How to track your freelance time using orgmode -- How to create the basic infrastructure for invoice generation -- How to generate the invoice -- How to manage multiple clients -- How to enter the finance details into your accounting software -- How to track invoice payments - -We will use the following packages: - -- Emacs+orgmode (duh?) -- yasnippet -- python layer (I use spacemacs, so whatever is the equivalent in your config) -- Some unnecessary Shakespearean references</description><url>https://emacsconf.org/2021/talks/invoice</url><persons><person>Bala Ramadurai</person></persons></event><event id="24" guid="e4e995c0-6e06-8544-a8c3-5f9a06c856fb"><date>2021-11-27T20:29:00Z</date><start>15:29</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-dashboard</slug><duration>0:10</duration><title>Productivity Dashboards with Emacs and Kindle</title><abstract></abstract><description>Times are approximate and will probably change. - -# Productivity Dashboards with Emacs and Kindle -Mehmet Tekman - - - -Since 2008, Amazon have released a new Kindle device every year, -supplanting each generation with a newer model that boasts highly -promoted incremental features which greatly devalues the price of -their older models. These forgotten models are sold on Ebay and -other secondhand websites at highly discount prices by owners who -do not see the true potential of these devices: Kindles are -excellent high contrast low-refresh display rate E-Ink devices, -with Wifi capability, that run embedded Linux in the -background. Depending on the model, an idle Kindle can last weeks -before needing a recharge. This makes them ideal as passive image -devices that can be configured easily using a few shell -scripts. Indeed, efforts have been made in dedicated hacker forums -to expose the Linux filesystem and to enable features such as -custom screensavers, SSH networking, and more. By exploiting these -features, and by carefully disabling the software/bloatware that -comes with the device, these Kindles have found new life as online -dashboard devices which can fetch and display information from the -internet at timely intervals. - -Here we describe a tool to control multiple Kindle devices with a -single org-mode/shell-based tool, built initially to periodically -serve updated Emacs Org-Agenda views, but later expanded to produce -online local weather reports and work calendar, Emacs calendars -(calfw, org-gcal), daily dietary information (org-calories), -Org-Mode sparse TODO trees, miscellaneous image and text content -(via imagemagick), small messages, and much more. - -In this talk, we show how to configure multiple Kindles with any -desired custom content, following any daily/weekly schedule, all -easily managed from Emacs within a single Org-Mode file. - - - -# Outline - -- 5-10 minutes: - - 1-3 mins - Talk about repurposing Kindles: - - - Cheap second-hand wifi device, hackable - - Low-powered, long battery life, low refresh rate &#x2013; perfect - for a dashboard - - Timely updated Org-Mode Agendas anyone? - - Reference to inspired projects (kindle-dashboard) - - 2-3 mins - Generate content - - - A static text+picture image easily generated with imagemagick - wrapper - - An image of a sparse tree of org-mode TODO file - - An image of another emacs view (e.g. Calfw, or org-calories) - - Show post-processing for optimizing image for Kindles - - 1-2 mins - Configuration in a single org-mode file - - - Defining Machines - - Defining Commands to generate content - - Defining Schedules to run Commands on multiple Machines at - specific points in the day - - 1-2 mins - Export and Run: - - - Show exported shell configs and generated cronjobs - - Witness multiple Kindles producing desired content with wakeup - timers</description><url>https://emacsconf.org/2021/talks/dashboard</url><persons><person>Mehmet Tekman</person></persons></event><event id="25" guid="33776e08-e815-db94-971b-a151236e11be"><date>2021-11-27T20:42:00Z</date><start>15:42</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-nyxt</slug><duration>0:10</duration><title>Emacs with Nyxt: extend your editor with the power of a Lisp browser</title><abstract></abstract><description>Times are approximate and will probably change. - -# Emacs with Nyxt: extend your editor with the power of a Lisp browser -Andrea mailto:andrea-dev@hotmail.com - pronouns: he/him -- https://ag91.github.io - - - -In 2021 browsers are essential if you use a computer. Even if Emacs -users love text as a format, they may need to shop and video call from -time to time (even more so in a pandemic!). Some of us modified their -browsers to at least have the same keybindings as our editor of -choice. What if I told you there is an Emacsy browser in the making? -What if you could "ace-jump" within a web page? What if you could run -a REPL to extend your browser while browsing? What if you could record -macros?! The browser exists: its name is Nyxt! - -In this talk I will share why it has great potential, how you can -integrate it with Emacs, and how you can migrate your Emacs mastery to -the web! - -If you were wishing for a Lispy and Emacsy browser, you should not -miss this talk! - -You can learn more about this at: <https://github.com/ag91/emacs-with-nyxt> - - - -# Outline - -- 5-10 minutes: quick demo of running Nyxt from Emacs and a little explanation of the code necessary for integration</description><url>https://emacsconf.org/2021/talks/nyxt</url><persons><person>Andrea</person></persons></event><event id="26" guid="86d4470a-8d19-7bd4-0c53-6aba1b49baef"><date>2021-11-27T20:55:00Z</date><start>15:55</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-design</slug><duration>0:10</duration><title>On the design of text editors</title><abstract></abstract><description>Times are approximate and will probably change. - -# On the design of text editors -Nicolas P. Rougier - - - -Text editors are written by and for developers. They come -with a large set of default and implicit choices in terms of layout, -typography, colorization and interaction that hardly change from one -editor to the other. It is not clear if these implicit choices derive -from the ignorance of alternatives or if they derive from developers' -habits, reproducing what they are used to. Durint this talk, I will -characterize these implicit choices and illustrate what are some -alternatives using GNU Emacs. - -# Outline - -1. Review of a "modern" code editor (5mn) -2. Introduction of an alternative using Emacs (5mn) - -## Links from the slides: - -* [Elegant Emacs](https://github.com/rougier/elegant-emacs) (https://github.com/rougier/elegant-emacs) -* [On the Design of Text Editors](https://arxiv.org/abs/2008.06030) (https://arxiv.org/abs/2008.06030) -* [N Λ N O Emacs](https://github.com/rougier/nano-emacs) (https://github.com/rougier/nano-emacs) -* [svg-lib (ELPA)](https://elpa.gnu.org/packages/svg-lib.html) (https://elpa.gnu.org/packages/svg-lib.html) -* [nano-theme (ELPA)](https://elpa.gnu.org/packages/nano-theme.html) (https://elpa.gnu.org/packages/nano-theme.html) -* [nano-modeline (ELPA)](https://elpa.gnu.org/packages/nano-modeline.html) (https://elpa.gnu.org/packages/nano-modeline.html) -* [nano-agenda (ELPA)](https://elpa.gnu.org/packages/nano-agenda.html) (https://elpa.gnu.org/packages/nano-agenda.html) - -## Contact information -* Contact [nicolas.rougier@inria.fr](mailto:nicolas.rougier@inria.fr) -* Follow my work at [github.com/rougier](https://github.com/rougier) -* Support my work at [github.com/sponsors/rougier](https://github.com/sponsors/rougier) or [en.liberapay.com/rougier/](https://en.liberapay.com/rougier/)</description><url>https://emacsconf.org/2021/talks/design</url><persons><person>Nicolas P. Rougier</person></persons></event><event id="53" guid="59e4daca-1e46-9054-9573-9c91966d6987"><date>2021-11-27T21:09:00Z</date><start>16:09</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-dev-update</slug><duration>0:08</duration><title>Emacs development updates</title><abstract></abstract><description>Times are approximate and will probably change. - -# Emacs development updates -John Wiegley</description><url>https://emacsconf.org/2021/talks/dev-update</url><persons><person>John Wiegley</person></persons></event><event id="27" guid="48a8580f-52ce-cc84-6a23-1eddf720ae02"><date>2021-11-27T21:20:00Z</date><start>16:20</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-freedom</slug><duration>0:38</duration><title>How Emacs made me appreciate software freedom</title><abstract></abstract><description>Times are approximate and will probably change. - -# How Emacs made me appreciate software freedom -Protesilaos Stavrou - - - -The theme will be "how Emacs empowered my software freedom". -I will outline the key moments in my transition to a GNU/Linux operating -system and mark those which eventually contributed towards me becoming -an Emacs user, maintainer of a&#x2014;dare I say&#x2014;popular package, and -contributor to upstream Emacs (among others). By alluding to personal -experiences, I will draw generalisable insights and connect them to what -I believe are irreducible qualities of Emacs qua software and Emacs as a -community of like-minded people. The talk will be theoretical in -nature: there won't be any code-related demonstration nor technical -references that only people with a background in computer science would -likely recognise. Personal anecdotes shall be tangential to the point -and considered as ancillary to the thesis of what Emacs represents from -the standpoint of software freedom and user empowerment. The -presentation is intended for a general audience that is interested in -GNU software in general and Emacs in particular. My formal educational -background as a social scientist (i.e. not a programmer) and later as a -philosopher informs my approach to this topic. - -The presentation shall be 40 minutes long. Its text will be in essay -form and shall be supplied as complementary material to the video. The -notation will be in Org mode. I cannot provide an outline in advance, -as it will most likely not be consistent with the actual presentation. -If, however, this is absolutely required for administrative purposes I -shall furnish one regardless with the proviso that I am in no way bound -by it and thus reserve the right to modify it ahead of the main event.</description><url>https://emacsconf.org/2021/talks/freedom</url><persons><person>Protesilaos Stavrou</person></persons></event><event id="28" guid="5287b003-f368-36c4-4f9b-8135734cad39"><date>2021-11-27T22:00:00Z</date><start>17:00</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-day1-close</slug><duration>0:05</duration><title>Closing remarks day 1</title><abstract></abstract><description>Times are approximate and will probably change. - -# Closing remarks day 1</description><url>https://emacsconf.org/2021/talks/day1-close</url><persons><person>EmacsConf</person></persons></event></room></day><day date="2021-11-28" start="2021-11-28T14:00:00Z" end="2021-11-28T22:00:00Z" index="2"><room name="Main"><event id="30" guid="d877a57a-14cf-a194-99c3-a344ecb24acc"><date>2021-11-28T14:00:00Z</date><start>09:00</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-day2-open</slug><duration>0:05</duration><title>Opening remarks day 2</title><abstract></abstract><description>Times are approximate and will probably change. - -# Opening remarks day 2</description><url>https://emacsconf.org/2021/talks/day2-open</url><persons><person>EmacsConf</person></persons></event><event id="31" guid="35d1d9e4-dfdf-f254-6aab-7a466fbfaf09"><date>2021-11-28T14:05:00Z</date><start>09:05</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-faster</slug><duration>0:20</duration><title>How to write faster Emacs Lisp</title><abstract></abstract><description>Times are approximate and will probably change. - -# How to write faster Emacs Lisp -Dmitry Gutov - - - -- Before optimizing, benchmark first. -- Different benchmarking approaches. -- Live evaluation, step-debugging, measuring from a debugger breakpoint. -- How to determine if a function is expensive. How to pick one from - competing alternatives (cl-lib, seq, dash, lean core). -- Print-benchmarking. -- Byte-compiled code can give a very different picture, changing where - the bottleneck is. How to quickly load a byte-compiled version. -- Steps taken to speed up the Xref package recently.</description><url>https://emacsconf.org/2021/talks/faster</url><persons><person>Dmitry Gutov</person></persons></event><event id="33" guid="599ef3fa-4c73-6c94-4953-75bbc7830681"><date>2021-11-28T14:30:00Z</date><start>09:30</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-structural</slug><duration>0:11</duration><title>Tree-edit: Structural editing for Java, Python, C, and beyond!</title><abstract></abstract><description>Times are approximate and will probably change. - -# Tree-edit: Structural editing for Java, Python, C, and beyond! -Ethan Leba - - - -In this talk, I'll discuss a vision for how writing code could be, where the -editing operations map directly to the primitives of the language itself -- and -my humble attempt of implementing this vision. _tree-edit_ seeks to provides a -structural editing plugin supporting conceivably any language with a tree-sitter -parser. - -**Structural editing does not have to be relegated to lisps or niche DSLs.** - -I liken the state of code editing today to writing assembly. The reason why -people like Python more than assembly is that for most purposes, the building -blocks of the language are mismatched with our thought process. We don't think -in terms of registers and addresses, we think in terms of variables, functions, -etc. So when we write and edit code, why do we edit in terms of deleting, -inserting, replacing characters &#x2013; not wrapping, inserting, raising, -deleting expressions and statements? - -I'll also discuss the implementation of tree-edit, which uses a novel -combination of the fantastic -[tree-sitter](https://github.com/emacs-tree-sitter/elisp-tree-sitter) parser -with an embedded logic programming DSL ([miniKanren](http://minikanren.org/), -using elisp port [reazon](https://github.com/nickdrozd/reazon)) to power it's -syntax tree generation. - -Check out the GitHub repo [here](https://github.com/ethan-leba/tree-edit)! - -# Outline - -- Discuss motivation (Why should I care?) -- Demonstrate tree-edit (Live-coding with tree-edit) -- Demonstrate tree-edit syntax tree generator (Elevator pitch on miniKanren)</description><url>https://emacsconf.org/2021/talks/structural</url><persons><person>Ethan Leba</person></persons></event><event id="32" guid="29d45a6f-9425-f5a4-bd23-297292e4ab7a"><date>2021-11-28T14:43:00Z</date><start>09:43</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-dsl</slug><duration>0:20</duration><title>Self-Describing Smart DSL's: The Next Magits</title><abstract></abstract><description>Times are approximate and will probably change. - -# Self-Describing Smart DSL's: The Next Magits -Psionic - - - -When we begin programming, the promise is to automate away repetitive -tasks in life. As those program's capability grows, we begin to need -configuration UI's. We can start with a CLI, but as any CLI grows, we -run into the following issues: - -- As options pile up, the intuition of simplicity is lost in helps and -manpages - -- Stateless operation has no idea what to do next and loses terseness -- Frequent dispatch of commands to interrogate state required for the -operator to decide what action to perform - -- Composition compounds with all of these issues - -Magit has the UI trifecta of being terse, intuitive, and intelligent. -Magit's UI input library, Transient, is a standalone package for -developing more killer UI's, and not just for CLI applications, but -also for server applications, Emacs applications, and Emacs itself. - -While Transient's potential is to create the most highly productive -UI's short of thought control, going beyond simple command dispatchers -requires a deeper dive. When we think like constructing a DSL for the -task and using transient to input that DSL, we get an intelligent, -self-describing modal programming system. - - -# Outline - -- Updates to Transient documentation and demos of API examples -- Wrapping a custom CLI tool in Transient</description><url>https://emacsconf.org/2021/talks/dsl</url><persons><person>Psionic</person></persons></event><event id="34" guid="8f62e571-91da-bd14-e7c3-b445c7b19d23"><date>2021-11-28T15:06:00Z</date><start>10:06</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-ui</slug><duration>0:10</duration><title>"Yak-shaving to a UI framework" (/"Help! I accidentally yak-shaved my way to writing a UI framework because overlays were slow")</title><abstract></abstract><description>Times are approximate and will probably change. - -# "Yak-shaving to a UI framework" (/"Help! I accidentally yak-shaved my way to writing a UI framework because overlays were slow") -Erik Anderson - - - -Tui.el is a textual User Interface (UI) framework for Emacs Lisp -modeled after the popular JavaScript 'React' framework. This package -implements React Component API's with the goal of simplifying -development of interactive UI's for all Emacs users- regardless of -their prior experience with React or web programming. Components -provide a useful functional unit for constructing complex interfaces -declaratively and also eliminate much of the burden associated with -updating textual content as application state changes. This talk will -cover use of the tui.el API and its operation in a textual environment -by implementing some basic UI's. - - - -# Outline - -- 5-10 minutes: - - Problem space: UI implementation complexity. - - API introduction: Displaying content, Components. - - Visual taste of dashboards and applications built with tui.</description><url>https://emacsconf.org/2021/talks/ui</url><persons><person>Erik Anderson</person></persons></event><event id="35" guid="b073d391-6c37-6bf4-7afb-47edc79631a9"><date>2021-11-28T15:19:00Z</date><start>10:19</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-rust</slug><duration>0:20</duration><title>Extending Emacs in Rust with Dynamic Modules</title><abstract></abstract><description>Times are approximate and will probably change. - -# Extending Emacs in Rust with Dynamic Modules -Tuấn-Anh Nguyễn - - - -Dynamic module support has been available since Emacs 25. It can be -used to extend Emacs with native libraries, for performance, -OS-specific features, or other functionalities that would take a lot -of time to re-implement in Lisp. The officially supported language is -C, which is tedious and error-prone to use. This talk discusses a -**safe** alternative that is also a lot **more convenient**: writing these -dynamic modules in Rust. - - - -# Outline - -- Walking through creating **a simple dynamic module** in - Rust, including setting up CI. -- Going through and explaining the **available APIs**.</description><url>https://emacsconf.org/2021/talks/rust</url><persons><person>Tuấn-Anh Nguyễn</person></persons></event><event id="38" guid="e7981936-6d72-93d4-8783-5ac64a0ae5bb"><date>2021-11-28T15:44:00Z</date><start>10:44</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-eaf</slug><duration>0:10</duration><title>Emacs Application Framework: A 2021 Update</title><abstract></abstract><description>Times are approximate and will probably change. - -# Emacs Application Framework: A 2021 Update -Matthew Zeng - - - -Emacs Application Framework (EAF) is a customizable and extensible GUI -application framework that extends Emacs graphical capabilities using -PyQt5. There are many new but important updates since EmacsConf2020 -last year, this talk will briefly go over them. - - - -# Outline - -- 5-10 minutes: (brief description/outline)</description><url>https://emacsconf.org/2021/talks/eaf</url><persons><person>Matthew Zeng</person></persons></event><event id="47" guid="5e1baaaf-56a3-b5b4-31cb-5437cf465cf9"><date>2021-11-28T15:58:00Z</date><start>10:58</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-model</slug><duration>0:10</duration><title>Extending the "model" of Emacs to other applications</title><abstract></abstract><description>Times are approximate and will probably change. - -# Extending the "model" of Emacs to other applications -Laszlo Krajnikovszkij - - - -Emacs is a great operating environment in a sense that it provides consistency -across different tools and applications within the Emacs ecosystem, as well as -external apps that can be integrated into it. It is also the most truly -malleable environment, each element of which can be adjusted or extended, -therefore providing the user with more power and freedom in personal computing. -Emacs definitely can be considered one of greatest software products in -existence. - -As a non-programmer, having had the chance to stumble upon Emacs a couple of -years ago, the only regret to have is that it didn't happen earlier. The definite -killer feature of Emacs - Org-mode, is what draws many of the less technical -folks to join the party and gradually start to use Emacs for writing documents, -whether personal or work related, manage tasks, emails and potentially everything -else. The learning curve and difference in approach, however, leaves some -potential users too scared of the arcane interface even with all it's quirks and -features because it requires at least some technical skills to understand and -use properly, and does not have an easy way to connect with external tools that -most people are forced to use for work. - -This talk proposes some ideas about how the model of Emacs, it's focus on -consistency, extensibility, as well as it's powerful interaction model can be -carried over to make modern interfaces, whether desktop or web applications, -that would be designed with a goal of reflecting the spirit of Emacs in terms of -the aforementioned features it possesses, and therefore enhance the capabilities -of the Emacs, while at the same time utilizing it as a backend for -text-processing and editing to a large extent. It would be really great to have -a personal web-interface for using modern task management tools, chats, emails -and such, but from a UI defined by the user. The goal is to use it on a desktop -or mobile, locally or self-hosted on a server, with support for touch and -gesture-based workflows, while preserving the Emacs philosophy and allowing to -seamlessly switch between Emacs and its web extension - -The proposed solution is to integrate more of the modern tools with Emacs, -utilize Org-mode as a way to define application-specific parameters for these -tools through Org properties, and then utilize these parameters for making a -modern local frontend that would enhance Emacs UI while allowing to use external -tools in a more personal and freedom respecting way (making the originals -obsolete over time). The talk serves the purpose of inviting community members to -a discussion about how Emacs can become more modern, more approachable by people -who don't possess the neccessarry technical skills to adjust it themselves, but -are keen to learn it, and potentially how to attract more users to greater -productivity, computer literacy and the ideas of free software. - - - -# Outline - -- 5-10 minutes - - Introduction - - Issues with most modern tools for work - - Issues with Emacs as a tool for work - - In search for a hybrid approach - - User controlled web-apps - - Opinions encouraged - - Contacts</description><url>https://emacsconf.org/2021/talks/model</url><persons><person>Laszlo Krajnikovszkij</person></persons></event><event id="50" guid="4cd6de26-cf48-95c4-9d3b-28895a43ec53"><date>2021-11-28T16:11:00Z</date><start>11:11</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-devel</slug><duration>0:20</duration><title>Don't write that package! or: How I learned to stop worrying and love emacs-devel</title><abstract></abstract><description>Times are approximate and will probably change. - -# Don't write that package! or: How I learned to stop worrying and love emacs-devel -Stefan Kangas - - - -We need a successful Emacs on this planet. This means that we need an -excellent out-of-the-box experience -- one that just works, but that you -can still hack and customize. There is so much great experimentation -and work going on out there in the wider Emacs community, but we would -be even better off if more of that could go into Emacs itself. - -Emacs' greatest strength is unfortunately sometimes also its greatest -weakness: it is *too* hackable. - -On occasion, people out there add stuff to their Init file to fix this -or that annoyance, or even bug. The more ambitious might go on to -package up such fixes: "Hey, 'foo-mode' doesn't have support for -'bookmark-set', let's write a package!" I am here to suggest that you -should not do that. - -You should submit a patch to Emacs! Maybe more people have that same -problem or annoyance, and would benefit from your solution? - -It is sometimes perceived as hard to contribute to Emacs core. I want -to encourage more people to get involved, and show that the barrier to -entry is really not that high. If I can do it, you can do it too! - -So should you really write that package, or should you stop worrying and -learn to love emacs-devel? Listen to my talk to find out more!</description><url>https://emacsconf.org/2021/talks/devel</url><persons><person>Stefan Kangas</person></persons></event><event id="36" guid="49a35f05-b71f-1d14-2343-a6638bec0d08"><date>2021-11-28T16:36:00Z</date><start>11:36</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-bindat</slug><duration>0:30</duration><title>Turbo Bindat</title><abstract></abstract><description>Times are approximate and will probably change. - -# Turbo Bindat -Stefan Monnier - - - - -# Table of Contents - - - -Bindat is an ELisp library to help manipulate binary data. This is a -niche library that is used by packages such as Websocket, EMMS, and -cpio-mode. Its implementation was repeatedly caught harassing hapless -kitten while at the same time providing poor service slowly. For -Emacs-28, Bindat was rewritten so as to make it more efficient and -flexible while respecting the kitten. In this presentation I intent to -show how we saved those. Not recommended for birds. - -- ~20 minutes: - 5 min: Intro and presentation of Bindat - 5 min: Showcase some of its problems - 5 min: Present the new design - 5 min: Examples of what can be done with it</description><url>https://emacsconf.org/2021/talks/bindat</url><persons><person>Stefan Monnier</person></persons></event><event id="39" guid="1ddbe380-b4f3-2b84-3cc3-9e799536db8e"><date>2021-11-28T17:40:00Z</date><start>12:40</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-native</slug><duration>0:40</duration><title>Emacs Lisp native compiler, current status and future developments</title><abstract></abstract><description>Times are approximate and will probably change. - -# Emacs Lisp native compiler, current status and future developments -Andrea Corallo - - - -Emacs Lisp (Elisp) is the Lisp dialect used by the Emacs text editor -family. GNU Emacs is traditionally capable of executing Elisp code -either interpreted or byte-interpreted after it has been compiled to -byte-code. - -In this talk I'll discuss the Emacs Lisp native compiler. This feature -recently merged into the main Emacs development line allow for -automatically compiling and executing Elisp as native code. - -During the presentation I'll touch on: - -- design goals -- compiler and runtime design and implementation -- performance implications -- upstream process -- area of improvements and future developments - -Format: 40 minutes</description><url>https://emacsconf.org/2021/talks/native</url><persons><person>Andrea Corallo</person></persons></event><event id="40" guid="5947c3e9-93c1-1014-7ffb-aa0e0097e3e4"><date>2021-11-28T18:27:00Z</date><start>13:27</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-form</slug><duration>0:10</duration><title>Old McCarthy Had a Form</title><abstract></abstract><description>Times are approximate and will probably change. - -# Old McCarthy Had a Form -Ian Eure - - - -Most practical languages are multi-paradigm, offering several -abstractions for the programmer. But did you know that Emacs Lisp -comes with a powerful system for object-oriented programming? Join me -for a discussion of EIEIO, and learn how it can help you write more -modular, flexible Emacs Lisp. - - - -# Outline - -- 5-10 minutes: (brief description/outline) - - What is CLOS/EIEIO? - - Why would I want OOP in Emacs Lisp? - - How is the CLOS object model different from C++/Java/.NET? - - Further reading</description><url>https://emacsconf.org/2021/talks/form</url><persons><person>Ian Eure</person></persons></event><event id="37" guid="5e162d34-ea19-8544-b693-dd6da0e885cd"><date>2021-11-28T18:41:00Z</date><start>13:41</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-test</slug><duration>0:05</duration><title>Test blocks</title><abstract></abstract><description>Times are approximate and will probably change. - -# Test blocks -Eduardo Ochs - - - -In this presentation I will show an idea that feels completely obvious -once we see it, but that only occured to me after after using Emacs -and eev as my main interface to the computer for more than 20 years. -Take any interpreted language that supports multi-line comments, and -whose interpreter can be run in an Emacs buffer - for example Lua, -Haskell, Python, or Julia; let's say just "Lua" from here on for -simplicity. So: suppose that we have a Lua script that we wrote, that -is called "foo.lua" and that defines lots of functions and defines the -classes Bar and Bletch. We can put after the definition of the class -Bar a multi-line comment that contains an eepitch block that when -executed starts a Lua interpreter, loads the script foo.lua (by -running 'dofile "foo.lua"'), and then has several tests for that class -and its methods; and we can put another block with tests like that -after the class Bletch, and other blocks after some functions. Eepitch -allows sending these tests line by line to the Lua interpreter by -typing <f8\> on each line that we want to send, and this lets us create -tests that are very easy to understand even without writing comments; -this gives us a very quick way to document code by executable tests, -that is super-great for experimental code that is still going to -change a lot before running the risk of being read by other people. - -These multi-line comments with eepitch blocks that run an interpreter -and make it load the current file are called "test blocks". The -command \`M-x eeit' inserts a test block at point, using the major mode -to decide the right syntax to use for the multi-line comments and for -the "dofile". We can configure the syntax of the test blocks for the -current major mode by running \`M-x find-eeit-links'; this can also be -used to add support for test blocks to more languages (or, more -precisely: to more major modes). - -Eduardo Ochs <http://angg.twu.net/emacsconf2021.html></description><url>https://emacsconf.org/2021/talks/test</url><persons><person>Eduardo Ochs</person></persons></event><event id="41" guid="51023225-018f-cf24-9d73-3c267907c13e"><date>2021-11-28T18:49:00Z</date><start>13:49</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-bug</slug><duration>0:20</duration><title>Let's talk about bug trackers</title><abstract></abstract><description>Times are approximate and will probably change. - -# Let's talk about bug trackers -Bastien Guerry - - - -For 17 years, the Org developers didn't use a bug tracker, -shamelessly failing the Joel Spolsky test. Why was it "good enough"? -Why was it wrong? Why did we move to Woof!? Why Woof! is not a bug -tracker? - -- 20 minutes</description><url>https://emacsconf.org/2021/talks/bug</url><persons><person>Bastien Guerry</person></persons></event><event id="42" guid="1407591a-29fd-3f64-1beb-01dea6e9d7d2"><date>2021-11-28T19:16:00Z</date><start>14:16</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-bidi</slug><duration>0:20</duration><title>Perso-Arabic Input Methods And Making More Emacs Apps BIDI Aware</title><abstract></abstract><description>Times are approximate and will probably change. - -# Perso-Arabic Input Methods And BIDI Aware Apps -Mohsen BANAN -- محسن بنان - - - -Emacs is a multilingual user environment. A true multilingual editor must -support bidirectionality and shaping of characters. Perso-Arabic scripts require -both of these features. - -Starting with Emacs 24, full native bidi -(bidirectional) support became available. For -many years prior to that Unicode support was -available and by around year 2000, reasonable -open-source shaping libraries were also available. - -With these in place at around 2012, I developed -two Persian input methods for emacs. These input -methods or variations of them can also be used for -Arabic and other Perso-Arabic scripts. - -With all of these in place, Emacs has now become -the ne plus ultra Libre-Halaal and Convivial usage -environment for Perso-Arabic users. - -Since emacs comes loaded with everything (Gnus -for email, Bbdb for address books, XeLaTeX modes -for typesetting, org-mode for organization, spell -checkers, completion systems, calendar, etc.), all basic -computing and communication needs of Perso-Arabic -users can be addressed in one place and -cohesively. - -In this talk I will demonstrate what a wonderful -environment that can be. - -My talk will be in two parts. - -In Part 1, I cover Persian input methods. With an emphasis on "Banan -Multi-Character (Reverse) Transliteration Persian Input Method". The -software is part of base emacs distribution. Full documentation is available -at: - - Persian Input Methods - For Emacs And More Broadly Speaking - شیوه‌هایِ درج به فارسی‌ - <http://mohsen.1.banan.byname.net/PLPC/120036> - -In Part 2, I'll demonstrate that Emacs is far more than an editor. Emacs can be -a complete Perso-Arabic usage environment. I will also cover the ramifications -of bidi on existing emacs applications, including: - -- Spell Checking, Dictionaries And Completion Frameworks: - - Existing emacs facilities can be extended to cover Perso-Arabic. - -- Gnus: - - Perso-Arabic rich email sending in HTML. - - Ramifications of bidi on from:, to: and subject: lines. - -- Bbdb: Ramifications of bidi on display and completion. - -- Calendar: - - Ramifications of bidi on display. - - Use of Persian text for Persian (solar) calendar. - - Use of Arabic text for Muslem (lunar) calendar. - -- AUCTeX: Persian typesetting with XeLaTeX - - Option of having right-to-left Perso-Arabic aliases for all latex commands. - -References: - - - Persian Input Methods: - <http://mohsen.1.banan.byname.net/PLPC/120036> - <http://www.persoarabic.org/PLPC/120036> -- Persian Input Methods Access Page - <http://www.persoarabic.org> -- Various Perso-Arabic resources - <http://www.freeprotocols.org/Repub/fpf-isiri-6219> -- Re-Publication Of - Persian Information Interchange and Display Mechanism, using Unicode - <https://github.com/bx-blee/persian-input-method> -- Git repo for - persian.el -- Quail package for inputting Persian/Farsi keyboards - - - BIDI: - <http://www.unicode.org/reports/tr9/> -- Annex #9 of the Unicode standard - <https://www.gnu.org/software/emacs/manual/html_node/elisp/Bidirectional-Display.html> - Emacs Bidirectional Display - - - Blee and Persian-Blee: - <https://github.com/bx-blee/env2> -- Very messy work-in-progress git repo for: - Blee: By* Libre-Halaal Emacs Environment - <http://www.by-star.net> -- A Moral Alternative To The Proprietary American Digital Ecosystem - <http://mohsen.1.banan.byname.net/PLPC/120033> -- - Nature of Polyexistentials: - Basis for Abolishment of The Western Intellectual Property Rights Regime - <http://mohsen.1.banan.byname.net/PLPC/120039> -- Defining The Libre-Halaal Label - - - Mohsen BANAN -- محسن بنان: - <http://mohsen.1.banan.byname.net/> -- Globish - <http://mohsen.1.banan.byname.net/persian> -- Farsi - <http://mohsen.1.banan.byname.net/french> -- French</description><url>https://emacsconf.org/2021/talks/bidi</url><persons><person>Mohsen BANAN</person></persons></event><event id="43" guid="3364aedb-a496-5c64-5383-b0080afa6d7b"><date>2021-11-28T19:41:00Z</date><start>14:41</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-mold</slug><duration>0:10</duration><title>Moldable Emacs, a step towards sustainable software</title><abstract></abstract><description>Times are approximate and will probably change. - -# Moldable Emacs, a step towards sustainable software -Andrea mailto:andrea-dev@hotmail.com - pronouns: he/him -- https://ag91.github.io - - - -We could learn about things better. Mountains of knowledge hide in -places we cannot access or use. The more we write down, the more it -takes to find and understand things we find useful. - -Knowledge (web, software, books) keeps growing faster and faster! This -is not sustainable: we cannot keep up with it! What if we repeat the -error of somebody else, only because it would take too much reading to -know? What if that knowledge is in some code we work with everyday? - -Moldable development is a paradigm shift that attempts to solve this -problem. In a gist, the tool you use should let you create special tools -to learn smartly from what you have already. - -Since we use Emacs, let's make our great editor moldable! - -This talk shows my progress in making Emacs closer to such a tool. We -are going to see how we can mold structured (and maybe even natural) -text to learn better, how we can inject notes in our projects and how -self documenting this tool is! - -I aim to inspire you to find a quicker way to learn from our digital -world! - -You can learn more about this at: <https://github.com/ag91/moldable-emacs> - - - -# Outline - -- 5-10 minutes: quick demo of moldable-emacs</description><url>https://emacsconf.org/2021/talks/mold</url><persons><person>Andrea</person></persons></event><event id="44" guid="daf3570b-3df3-9db4-a1f3-ce98d9863717"><date>2021-11-28T19:55:00Z</date><start>14:55</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-clede</slug><duration>0:20</duration><title>CLEDE the Common Lisp Emacs Development Environment.</title><abstract></abstract><description>Times are approximate and will probably change. - -# CLEDE the Common Lisp Emacs Development Environment. -Fermin MF - - - -I've been developing a package that helps with the development of -Common Lisp's software, -it's uses the internal semantic framework, it has a custom reader -and integration for -common Emacs packages (like Sly and the internal inferior-lisp-mode). - -The idea is to supply features that other language with and static -analyzer have, -like refactoring and code generation. - -For more details: <https://gitlab.com/sasanidas/clede> - -- 20 minutes: - It seems like not too much people knows about semantic, so I can - summarize some of it in 10 minutes - and then An explanation on how to use the package, how to extend it - and the future of it.</description><url>https://emacsconf.org/2021/talks/clede</url><persons><person>Fermin MF</person></persons></event><event id="45" guid="f03ae971-4d2b-ccc4-2643-4ae2391ce1ab"><date>2021-11-28T20:22:00Z</date><start>15:22</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-imaginary</slug><duration>0:11</duration><title>Imaginary Programming</title><abstract></abstract><description>Times are approximate and will probably change. - -# Imaginary Programming -Shane Mulligan - - - -Imaginary Programming (IP) is both methodology and paradigm. It is an -extension of literate programming and a way of creating software without -the use of imperative, functional or even declarative code. Yet IP employs -all disciplines to achieve the miraculous. The only contingency is on one -or more language models, known as foundation models. The real value of IP -is not found by abandoning sound logic altogether, but in weaving the real -with the imaginary. The future of imaginary programming is one in which -almost all of computing is inferred. I have built a suite of tools based on -emacs for interfacing real programming languages with imaginary ones; all -of this in order to demonstrate what I mean; a ‘complex’ terminal that lets -you imagine what happens no matter how nested you are within interpreters, -an example-oriented language, a file format that encodes the provenance of -text and a library for imaginary functional programming primitives called -iLambda. It is important to recognise IP because, for lack of a better -term, it has far-reaching implications for intellectual property and the -GPL. Please keep an open mind. - - - -# Outline - -- 5-10 minutes: -- a 5 minute introduction to imaginary programming, followed by - - a demonstration of iLambda. - - iλ, a family of imaginary programming libraries - <https://mullikine.github.io/posts/designing-an-imaginary-programming-ip-library-for-emacs/> - - - -IRC libertyprime at #emacs on libera - -Shane Mulligan</description><url>https://emacsconf.org/2021/talks/imaginary</url><persons><person>Shane Mulligan</person></persons></event><event id="46" guid="27595637-b6b9-f764-805b-ff1b7f009006"><date>2021-11-28T20:36:00Z</date><start>15:36</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-build</slug><duration>0:20</duration><title>How to build an Emacs</title><abstract></abstract><description>Times are approximate and will probably change. - -# How to build an Emacs -Fermin MF - - - -This is a deep dive in the Emacs philosophical and technical -aspect on what makes our beloved GNU Emacs -what it it. It's also a talk about the early LISP machines and -fascinating were those days of experimentation and engineering. - -It will continue with the Emacs benefits/trade-offs from an -user/developer stand points, what things can be improved and -what can be an hypothetical path on how to build a software that -can also be called Emacs. - -As a last part, I'll talk about CEDAR, an Emacs that I've been -developing in Common Lisp, the project goals -and the challenges. - -For more details about CEDAR: <https://gitlab.com/sasanidas/cedar> - -- 40 minutes: - A dive into the Emacs/Lisp machines history, what makes GNU Emacs - an Emacs and how you can build an Emacs.</description><url>https://emacsconf.org/2021/talks/build</url><persons><person>Fermin MF</person></persons></event><event id="48" guid="80d1ad02-5fe4-03b4-c573-17ea6cdb61aa"><date>2021-11-28T21:03:00Z</date><start>16:03</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-forever</slug><duration>0:40</duration><title>M-x Forever: Why Emacs will outlast text editor trends</title><abstract></abstract><description>Times are approximate and will probably change. - -# M-x Forever: Why Emacs will outlast text editor trends -David Wilson - - - -The computer software industry has seen many "popular" text editors come -and go, often due to the mercurial fashions of software development. In -this talk, we'll take a look at why popular editors fade and the -specific aspects of Emacs that will ensure it remains relevant -regardless of mainstream popularity. - - - -# Outline - -- Discuss the core thesis, the features that make Emacs - desirable for long-term use (extensibility, day-to-day 'life' features) - -- Include more background on the text editor landscape and - how the scope of various editors is more narrow and doesn't compare to Emacs. - -- Talk about specific instances where editors were popular, fell out - of popularity, and why (due to changing fashions, not usually - better features).</description><url>https://emacsconf.org/2021/talks/forever</url><persons><person>David Wilson (System Crafters)</person></persons></event><event id="49" guid="828e7c62-8430-f1a4-431b-63c308d58688"><date>2021-11-28T21:50:00Z</date><start>16:50</start><language>en</language><room>Main</room><subtitle></subtitle><type>Talk</type><track>Main</track><slug>emacsconf-2021-talk-day2-close</slug><duration>0:10</duration><title>Closing remarks day 2</title><abstract></abstract><description>Times are approximate and will probably change. - -# Closing remarks day 2</description><url>https://emacsconf.org/2021/talks/day2-close</url><persons><person>EmacsConf</person></persons></event></room></day></schedule>
\ No newline at end of file +</description><url>https://emacsconf.org/2021/talks/day2-close</url><persons><person>EmacsConf</person></persons></event></room></day></schedule>
\ No newline at end of file diff --git a/2021/emacsconf.ics b/2021/emacsconf.ics index ea121645..10f83587 100644 --- a/2021/emacsconf.ics +++ b/2021/emacsconf.ics @@ -13,9 +13,9 @@ UID:dc07efcd-6d79-cfd4-fed3-59c885fe2922 URL:https://emacsconf.org/2021/talks/day1-open DTSTART:20211127T140000Z DTEND:20211127T140500Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/day1-open\n# Opening remarks + conf.org/2021/talks/day1-open\n END:VEVENT BEGIN:VEVENT SUMMARY:Emacs News Highlights - Sacha Chua @@ -25,16 +25,10 @@ UID:393ba3c2-b2a6-6a84-44eb-872aa333d08d URL:https://emacsconf.org/2021/talks/news DTSTART:20211127T140500Z DTEND:20211127T141000Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Sacha Chua":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/news\n# Emacs News Highlights\nSacha Chua <mailto:sach - a@sachachua.com> - pronouns: she/her\n\n\n\nQuick overview of Emacs commun - ity highlights since the last conference\n\nYou can find the links and ima - ges at\n<https://github.com/sachac/emacsconf-2021-emacs-news-highlights>\n - \nPosting the video early to help test formatting.\n\n\n\n# Questions\, an - swers\, and community-provided links\n\n<a name="transcript"></a>\n# Trans - cript + conf.org/2021/talks/news\n END:VEVENT BEGIN:VEVENT SUMMARY:The True Frownies are the Friends We Made Along the Way: An Anecdot @@ -45,29 +39,10 @@ UID:06df8309-bd04-eb24-d443-a780c56adc0a URL:https://emacsconf.org/2021/talks/frownies DTSTART:20211127T141100Z DTEND:20211127T143100Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Case Duckworth":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/frownies\n# The True Frownies are the Friends We Made - Along the Way: An Anecdote of Emacs's Malleability\nCase Duckworth\n\n\n\n - Emacs is well-known for being extremely flexible\, programmable\, and\next - ensible\; in fact\, that's probably the biggest reason it's still\nbeing u - sed after 40+ years of existence\, and even has enough clout to\ngenerate - an entire conference in its name. In this medium-length\npresentation\, I - will add another point to the data set proving Emacs's\nabilities\, by na - rrating the latest package I made\, \\`frowny.el\\`\, from\nits conception - to its current\, nearly-completed state.\n\nI wrote frowny.el to scratch - someone else's itch as a joke on IRC\, but\nit has been called "pretty use - ful\, for a joke package." I feel like\nthat encapsulates the spirit of E - macs and that's why I want to present\non this topic.\n\nAlong the way\, I - 'll discuss just a little of my own history of Emacs\,\nand why I feel it' - s a great tool for non-technical users to sink their\nteeth into.\n\n## Sp - eaker information\n\n- Name pronunciation: /keɪs ˈdʌkwə(ɹ)θ/ (CASE DUCK-wo - rth)\n- Prounouns: he/him\n- Homepage: <https://www.acdw.net>\n- Preferred - contact info: [email](mailto:acdw@acdw.net)\n- Links:\n - <https://bread - punk.club>\, a shared unix server about bread\n - [my Mastodon account](h - ttps://writing.exchange/@acdw) (though I'm moving to\n[tiny.tilde.website] - (https://tiny.tilde.website/@acdw) ... soon™) + conf.org/2021/talks/frownies\n END:VEVENT BEGIN:VEVENT SUMMARY:Emacs as Design Pattern Learning - Greta Goetz @@ -77,90 +52,10 @@ UID:fe959e43-441b-ed34-854b-87f6f481f55a URL:https://emacsconf.org/2021/talks/pattern DTSTART:20211127T143400Z DTEND:20211127T145800Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Greta Goetz":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/pattern\n# Emacs as Design Pattern Learning\nGreta Goe - tz\n\n\n\nHow do we manage today? This presentation is for people interest - ed in thinking about Emacs as a tool sophisticated enough to cater to the - complex assemblage of tasks\, people\, activities/outcomes\, tools (Markau - skaite & Goodyear). Some software oversimplifies. Emacs both helps users i - mplement design pattern learning that can cope with complexity while also - modeling design pattern learning. By championing the opportunity for users - to also be co-creators (cf. Beaty et al.)\, the free software design at t - he core and center of Emacs teaches us a way of "being" (Alexander\, Gabri - el) that can be extended to both the Emacs community and beyond\, in a kno - wledge of how to live (Stiegler\, Illich).\n\n1. Definition of design pat - terns and relation to Emacs\n2. Why this approach matters\n3. Managing c - omplexity: Emacs as mind map\n4. Emacs as design pattern framework\n5. P - ersonal customization\n6. Implementing Emacs as a model for learning\n7. - Emacs as accommodating complex social\, community assemblages\n\n# Refere - nces\n\n- Andler\, D. & Guerry\, B. (Eds.). *Apprendre demain: Sciences - cognitives et éducation à l’ère numérique*\, 137-154. Paris: Hatier.\n- - Alexander\, C. (1977). *A pattern language*. New York: Oxford University P - ress.\n- Alexander\, C. (1979). *The timeless way of building*. New York - : Oxford University Press.\n- Alexander\, C. (1993). *A foreshadowing of - 21st century art: The color and geometry of very early Turkish carpets*. - New York: Oxford University Press.\n- Beaty\, L.\, Cousin\, G.\, & Hodgs - on\, V. (2010). Revisiting the e-quality in networked learning manifesto. - In L. Dirckinck-Holmfeld\, V. Hodgson\, C. Jones\, M. de Laat\, D. McConne - ll\, & T. Ryberg (Eds.)\, *Proceedings of the 7th International Conference - on Networked Learning* (pp. 585–592). Aalborg: Lancaster University. http - ://www.lancs.ac.uk/fss/organisations/netlc/past/nlc2010/abstracts/PDFs/Bea - ty.pdf. Accessed 30 October 2021.\n- Chua\, S. (2021). Completing sketch - es. https://sachachua.com/dotemacs/#org092e0d5. Accessed 29 October 2021.\ - n- Crichton\, M. (1983). *Electronic life*. New York: Knopf.\n- Gabrie - l\, R. (1996). *Patterns of software*. New York\, Oxford: Oxford Universit - y Press.\n- Goodyear\, P. & Retalis\, S. (2010). Learning\, technology a - nd design. In Goodyear\, P. & Retalis\, S. (Eds.). *Technology-enhanced le - arning: Design patterns and pattern languages*\, 1-27. Rotterdam\, Boston: - Sense Publishers.\n- Guo\, P. (2018). Students\, systems\, and interact - ions: Synthesizing the first\nfour years of Learning@Scale and charting th - e future. L@S 2018\, June 26–28\, 2018\, London\, United Kingdom. DOI: htt - ps://doi.org/10.1145/3231644.3231662. <https://pg.ucsd.edu/pubs.htm>. Acce - ssed 25 October 2021.\n- Guo\, P.\, Kim\, J. & Rubin\, R. (2014). How vi - deo production affects student engagement: An empirical study of MOOC vide - os. ACM Conference on Learning at Scale. <https://pg.ucsd.edu/pubs.htm>. A - ccessed 25 October 2021.\n- Illich\, I. (1973). *Tools of conviviality*. - New York: Harper & Row.\n- Kim\, J.\, Guo\, P.\, Seaton\, D.\, Mitros\, - P.\, Gajos\, K. & Miller\, R. (2014). Understanding in-video dropouts and - interaction peaks in online lecture videos. ACM Conference on Learning at - Scale. <https://pg.ucsd.edu/pubs.htm>. Accessed 25 October 2021.\n- Mar - kauskaite\, L. & Goodyear\, P. (2017). *Epistemic fluency and professional - education: innovation\, knowledgeable action and actionable knowledge*. D - ordrecht: Springer.\n- Markel\, J. & Guo\, P. (2020). Designing the futu - re of experiential learning environments for a post-COVID world: A prelimi - nary case study. NFW ’20 (Symposium on the New Future of Work)\, August 3– - 5\, 2020\, Virtual Event. <https://pg.ucsd.edu/pubs.htm>. Accessed 25 Octo - ber 2021.\n- Morin\, E. ([2004] 2008). *La Méthode - tome 6: Éthique*. É - ditions du Seuil: Paris.\n- Planet Emacs Life. <https://planet.emacslife - .com/>. Accessed 25 October 2021\n- Stallman\, R. (2002). My Lisp experi - ences and the development of GNU Emacs. https://www.gnu.org/gnu/rms-lisp.e - n.html. Accessed 29 October 2021.\n- Stiegler\, B. (2018). *The neganthr - opocene*. Open Humanities Press.\n- Trocmé-Fabre\, H. (1999). *Réinvente - r le métier d’apprendre*. Paris: Éditions d’organisation.\n\n\n# Availabil - ity and preferred Q&A approach\n\nDue to the pandemic situation\, my teach - ing schedule fluctuates so I\nwill not know my availability until much clo - ser to the\ndate. Therefore\, I can only guarantee delayed answer response - \n(whatever you request)\, but if available\, will join live.\nMay I pleas - e note that I will be pre-recording my video if this submission is accepte - d.\n\n\n# Speaker release\n\nBy submitting this proposal\, I agree that my - presentation at\nEmacsConf 2021 is subject to the following terms and con - ditions:\n\nThe EmacsConf organizers may capture audio and video (a "Recor - ding")\nof my presentation and any associated materials\, which may includ - e\nslides\, notes\, transcripts\, and prerecording(s) of my presentation\n - that I provide to the EmacsConf organizers.\n\nI authorize the EmacsConf o - rganizers to distribute\, reproduce\,\npublicly display\, and prepare deri - vative works of the Recording and\nany derivative works of the Recording ( - the "Licensed Materials")\nunder the terms of the Creative Commons Attribu - tion-ShareAlike 4.0\nInternational (CC BY-SA 4.0) license.\n\nI grant to t - he EmacsConf organizers permission to use my name\,\nlikeness\, and biogra - phic information in association with their use\nof the Licensed Materials - under the above license.\n\nI represent that I have the authority to grant - the above license to\nthe EmacsConf organizers. If my presentation incorp - orates any\nmaterial owned by third parties\, I represent that the materia - l is\nsublicensable to the EmacsConf organizers or that my use of them is\ - nfair use. + conf.org/2021/talks/pattern\n END:VEVENT BEGIN:VEVENT SUMMARY:GNU's Not UNIX: Why Emacs Demonstrates The UNIX Philosophy Isn't Al @@ -171,26 +66,10 @@ UID:ea5bab3c-f31e-68a4-fa23-81ca67fa1990 URL:https://emacsconf.org/2021/talks/unix DTSTART:20211127T150000Z DTEND:20211127T150700Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Daniel Rose":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/unix\n# GNU's Not UNIX: Why Emacs Demonstrates The UNI - X Philosophy Isn't Always The Only Answer\nDaniel Rose\n\n\n\nThe talk tar - gets users who are curious about computational philosophies\,\nor those wh - o might not know how to best utilise Emacs conceptually. The\ntalk will co - ver what the UNIX philosophy is\, the GNU Free Software\nprinciples\, a ty - pical (Neo)Vi(m) user's approach\, and then how one might\naccomplish this - in Emacs combining the aformentioned ideals. The\nlisteners will learn ho - w they can approach Emacs ideologically\, and how\nblocking themselves int - o one philosophy or the other will limit their\nefficiency. Although you m - ay be a veteran GNU/Linux and Emacs user\,\nunderstanding how to use both - philosophies together will still allow you\nto be more performant than wit - hout.\n\n\n\n# Outline\n\n- How can one limit their usage of CLI tools w - hile still maintaining\n the ideals of both.\n- How using CLI too - ls can still perfectly flow into Emacs.\n- How having all programs in Em - acs and unified keybindings is akin\n to a terminal user.\n- Why - thinking about computational philosophies might itself be an\n impe - diment. + conf.org/2021/talks/unix\n END:VEVENT BEGIN:VEVENT SUMMARY:Emacs manuals translation and OmegaT - Jean-Christophe Helary @@ -200,57 +79,10 @@ UID:db4ccb28-867f-df24-c073-eaca6edad438 URL:https://emacsconf.org/2021/talks/omegat DTSTART:20211127T151100Z DTEND:20211127T152100Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Jean-Christophe Helary":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/omegat\n# Emacs manuals translation and OmegaT\nJean-C - hristophe Helary\n\n\n\nEven if it is generally agreed that software local - ization is a good thing\, Emacs is lacking in that respect for a number of - technical reasons. Nonetheless\, the free software using public could gre - atly benefit from Emacs manuals translations\, even if the interface were - to remain in English.\n\nOmegaT is a multiplatform GPL3+ "computer aided t - ranslation" (CAT) tool running on OpenJDK 8. CATs are roughly equivalent f - or translators to what IDEs are for code writers. Casual translators can b - enefit from their features but professionals or committed amateurs are the - most likely to make the most use of such tools.\n\nWhen OmegaT\, free sof - tware based forges and Emacs meet\, we have a free multi-user translation - environment that can easily sustain the (close to) 2 million words load th - at comprise the manuals distributed with Emacs\, along with powerful featu - res like arbitrary string protection for easy typing and QA (quality assur - ance)\, automatic legacy translation handling\, glossary management\, hist - ory based or predictive autocompletion\, etc.\n\nThe current trial project - for French is hosted on 2 different forges:\n\n1. sr.ht hosts the source - files\n <https://sr.ht/~brandelune/documentation_emacs/>\n2. chapril ho - sts the OmegaT team project architecture\n <https://forge.chapril.org/b - randelune/documentation_emacs>\n\nThe sources are regularly updated with a - po4a based shell script.\n\n# Outline\n\n- Duration: 10 minutes\n- Softwa - re used during the presentation\n - [po4a](https://po4a.org) a tool to co - nvert documentation formats to and from the commonly used `gettext` **PO** - format.\n po4a supports the `texinfo` format along with many others.\n - - [OmegaT](https://omegat.org) a "computer aided translation" tool used - by translators to efficiently combine translation resources (legacy transl - ations\, glossaries\, etc.) so as to produce more consistent translations. - \n\nDuring this short presentation\, I will address:\n\n- The specificitie - s of the Emacs manuals and the difficulties they present to the translator - \n- The reason why a professional tool is better than a collaborative web- - based system\n- How to convert the texi and org files to a format that tra - nslators can handle\n- How to adapt OmegaT to the Emacs manual specificiti - es\n- How to use OmegaT features such as arbitrary string protection\, leg - acy translation handling\, glossaries\, autocompletion\, QA\, etc.\n- How - to use OmegaT with a team of 2 (or more) translators working at the same t - ime\n\n\nI will *not* show:\n\n- How to create an OmegaT project\n- How to - set up an OmegaT team project\n- How to use OmegaT from the command line - to work in localization pipelines\n- How to use machine translation and MT - "post-edit"\n- How to convert back the translated files to texi format\n- - How to install translated texi files for use in Emacs\n\nPeople who are i - nterested in knowing more about OmegaT are invited to check the [online us - er manual](https://omegat.sourceforge.io/manual-latest/en/).\n\n# Personal - information\n- Name pronunciation: [ʒɑ̃kRstɔf elaRi](https://doublet.jp/w - p-content/uploads/2021/11/jch.ogg)\n- Pronouns: he\n- Homepage: [https://m - ac4translators.blogspot.com](https://mac4translators.blogspot.com)\n- Pref - erred contact info: [jean.christophe.helary@traduction-libre.org](jean.chr - istophe.helary@traduction-libre.org)\n- Links for sponsoring/supporting (m - ultilingual translations): [https://doublet.jp](https://doublet.jp) + conf.org/2021/talks/omegat\n END:VEVENT BEGIN:VEVENT SUMMARY:NonGNU ELPA Update - Philip Kaludercic @@ -260,17 +92,10 @@ UID:525d972d-1e34-bcb4-e9c3-861942549357 URL:https://emacsconf.org/2021/talks/nongnu DTSTART:20211127T152400Z DTEND:20211127T153100Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Philip Kaludercic":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/nongnu\n# NonGNU ELPA Update\nPhilip Kaludercic\n\n\n\ - nNonGNU ELPA was announced last year\, as a package repository\nthat will - be enabled by default in Emacs\, but doesn't require\nany copyright assign - ment. This means that a lot of popular\npackages can now be installed easi - er\, without any additional\nconfiguration.\n\nIn this talk I would like t - he give a reminder of what NonGNU\nELPA is and how it works\, update the p - articipants on what has\nhappened since last year and what maintainers hav - e to do if they\nwant their packages to be added to the repository. + conf.org/2021/talks/nongnu\n END:VEVENT BEGIN:VEVENT SUMMARY:Manual Package Management in The Era of Repositories - Why and How @@ -281,19 +106,10 @@ UID:245a575a-965a-caa4-8d3b-75f8519c2f3e URL:https://emacsconf.org/2021/talks/borg DTSTART:20211127T153600Z DTEND:20211127T154400Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Dhavan (codingquark)":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/borg\n# Manual Package Management in The Era of Reposi - tories - Why and How\nDhavan (codingquark)\n\n\n\nEmacs now has many packa - ge repositories - enought to have conflicts\nand arguments about. The pack - ages are becoming big\, they depend on many\nother packages and it is not - easy to keep track of what all is being\ninstalled in our Emacsen. An aggr - essive way out of this is to use Yet\nAnother Package and install all elis - p code manually - with borg[1].\n\n[1]: <https://github.com/emacscollectiv - e/borg>\n\n\n\n# Outline\n\n- 5-10 minutes: (brief description/outline)\ - n 1. What are we trying to solve?\n 2. What is borg?\n 3. How - to use it?\n 4. Assimilate a package for demo + conf.org/2021/talks/borg\n END:VEVENT BEGIN:VEVENT SUMMARY:telega.el and the Emacs community on Telegram - Gabriele Bozzola @@ -303,20 +119,10 @@ UID:86158391-53a2-7cb4-d7d3-020afbf6d8d9 URL:https://emacsconf.org/2021/talks/telega DTSTART:20211127T154800Z DTEND:20211127T155600Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Gabriele Bozzola":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/telega\n# telega.el and the Emacs community on Telegra - m\nGabriele Bozzola and Evgeny Zajcev\n\n\n\nTelegram is a cross-platform - instant messaging system. The large number of\nfeatures and the widespread - adoption make it a good choice for both private\nconversations with frien - ds and for large online communities. In this talk\, I\nam going to present - the Emacs community on Telegram and its initiatives. I\nam also going to - discuss telega.el\, the Emacs client for Telegram. telega.el\nis a high-qu - ality package that perfectly integrates in Emacs. It supports\nthe vast ma - jority of the features supported by the official clients\, while\nadding s - everal unique ones. In the talk\, I will present the package and\nhighligh - t some of the most important features. + conf.org/2021/talks/telega\n END:VEVENT BEGIN:VEVENT SUMMARY:Introducing N-Angulator - Kevin Haddock @@ -326,22 +132,10 @@ UID:e4bdc2c1-e4b6-67e4-aafb-87ec9aaf846b URL:https://emacsconf.org/2021/talks/nangulator DTSTART:20211127T155800Z DTEND:20211127T160800Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Kevin Haddock":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/nangulator\n# Introducing N-Angulator\nKevin Haddock\n - \n\n\nThe Unix file system is essentially an N-dimentional sparse array th - at\ncurrently lacks a decent editor and browser which\ncan effectively lev - erage the logical tri-angulation (or\, more properly\n"n-angulation") of a - toms/blobs within it.\n\nN-Angulator is the genesis\, to wit\, the "Model- - T\," of such a program.\n\n(see google drive link below for a very old unc - irculated prototype\nvideo demo. Be sure and turn the volume UP!)\n\nna. - intro.flv\n<https://drive.google.com/file/d/1EZN0Xs8eGlEbSIYFml2lp3GCNnmLQ - a98/view?usp=drive_web>\n\n\n\n# Outline\n\n- 5-10 minutes: (brief descr - iption/outline)\n\nThe reconceptualization of the Unix file system as the - N-Dimensional\nsparse array will be discussed.\n\nA simple pre-existing da - tabase will be queried.\n\nIf time\, questions will be entertained by vide - o/audio and/or IRC. + conf.org/2021/talks/nangulator\n END:VEVENT BEGIN:VEVENT SUMMARY:A day in the life of a janitor - Stefan Monnier @@ -351,21 +145,10 @@ UID:14ab7a54-d75d-45e4-85ab-8fd2e391ea41 URL:https://emacsconf.org/2021/talks/janitor DTSTART:20211127T161100Z DTEND:20211127T163700Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Stefan Monnier":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/janitor\n# A day in the life of a janitor\nStefan Monn - ier\n\n\n\nBecause of a reckless former Emacs maintainer that shall\n bet - ter stay unnamed\, ELisp has seen a fair bit of churn in the last 10\n ye - ars\, making it necessary to clean up "old" code [in order to open up\n t - he road for yet more recklessness? ].\n In this documentary we will follo - w a famous janitor in his every day job\n dealing with the aftermath of t - he cl-lib / lexical-binding party.\n\n- ~20 minutes\n Here really\, I - 'm not sure how much time this will take. I put 20\n minutes because I - think I might be able to fill that and I think more\n than that could - turn too boring. I intend to make it a "live coding"\n kind of thing\, - without anything like an outline: it's basically "make"\n followed by - fixing the warnings. + conf.org/2021/talks/janitor\n END:VEVENT BEGIN:VEVENT SUMMARY:How to help Emacs maintainers? - Bastien Guerry @@ -375,14 +158,10 @@ UID:51c360e6-188f-9a34-05bb-0a8d2eb09cdc URL:https://emacsconf.org/2021/talks/maintainers DTSTART:20211127T164200Z DTEND:20211127T165200Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Bastien Guerry":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/maintainers\n# How to help Emacs maintainers?\nBastien - Guerry\n\n\n\nAfter 11 years of helping as the Org maintainer\, I would\n - like to share a few lessons learned. My goal is help everyone take\ncare - of Emacs maintainance by taking care of Emacs maintainers.\n\n\n\n# Outlin - e\n\n- 5-10 minutes + conf.org/2021/talks/maintainers\n END:VEVENT BEGIN:VEVENT SUMMARY:Typesetting Gregorian Chant with Emacs - Spencer King @@ -392,22 +171,10 @@ UID:716d913f-de8b-91a4-5f33-e04ba0905fa5 URL:https://emacsconf.org/2021/talks/gregorian DTSTART:20211127T165500Z DTEND:20211127T170500Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Spencer King":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/gregorian\n# Typesetting Gregorian Chant with Emacs\nS - pencer King\n\n\n\nThere are a variety of methods for typesetting gregoria - n\nchant scores and outputting high-quality sheet music. One of these is\n - a tool called Gregorio\, which integrates with LaTeX allowing scores to\nb - e cleanly inserted into other documents. All Gregorio files are plain\ntex - t\, allowing them to easily be shared with other users and managed\nwith a - version control system. In this talk\, I will give a brief\noverview of t - he Gregorio tool and then show how it can be used in\nEmacs by typesetting - a simple score. All code and examples will be\nmade available to help new - users get started with typesetting their\nown scores.\n\n\n\n# Outline\n\ - n- 5-10 minutes: (brief description/outline)\n 1. Introduction to ch - ant music\n 2. Introduction to Gregorio\n 3. Example of typesettin - g a score in Emacs\n 4. Code and example availability + conf.org/2021/talks/gregorian\n END:VEVENT BEGIN:VEVENT SUMMARY:Emacs and Montessori Philosophy - Grant Shangreaux @@ -417,31 +184,10 @@ UID:6fccae45-04b5-5524-662b-fdba87754d06 URL:https://emacsconf.org/2021/talks/montessori DTSTART:20211127T173000Z DTEND:20211127T174000Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Grant Shangreaux":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/montessori\n# Emacs and Montessori Philosophy\n\n\n\n\ - nAs a former Montessori guide and now parent\, I often think about the\nre - lationship of this particular educational philosophy and how it manifests\ - nin my work with software\, Emacs in particular. This talk introduces the\ - nconcept of Emacs as an educational environment and how it expresses eleme - nts of\nMontessori psychology regarding "Human Tendencies". Human tendenci - es are innate\ndrives present in everybody that allow us to explore and ma - ke sense of our world.\n\n\n\n# Outline\n\n- 5-10 minutes: (brief descri - ption/outline)\n Quick overview of a Montessori classroom environment:\ - n\n - the adults or guides primarily observe and present material\n - - the children are free to explore materials as they choose (within li - mits)\n - the environment itself is prepared specifically to foster e - ngagement\n\n Enumerate the "Human Tendencies":\n\n - Abstraction\ - n - Activity\n - Communication\n - Exactness\n - Explo - ration\n - Manipulation (of the environment)\n - Order\n - - Orientation\n - Repetition\n - Self-Perfection\n - Work (al - so described as "purposeful activity")\n\n How does Emacs express these - things?\n\n - in the short version\, pose the question\, and perhaps - give one example.\n - Emacs is an environment that provides faciliti - es for individuals to\n find their way to proficiency through their - Human Tendencies.\n - We are all both learners and guides\, Emacs is - our classroom + conf.org/2021/talks/montessori\n END:VEVENT BEGIN:VEVENT SUMMARY:Emacs Research Group\, Season Zero: What we did together with Emacs @@ -453,31 +199,13 @@ UID:9cee7e43-bcb1-7f64-c40b-5f9ea938d11a URL:https://emacsconf.org/2021/talks/erg DTSTART:20211127T174300Z DTEND:20211127T175800Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Noorah Alhasan":invalid:nomail ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Joe Corneli":invalid:nomail ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Raymond Puzio":invalid:nomail ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Leo Vivier":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/erg\n# Emacs Research Group\, Season Zero: What we did - together with Emacs in 2 hours a week for a year\nNoorah Alhasan\, Joe Co - rneli\, Raymond Puzio\, Leo Vivier\n\n\n\nThe four of us met at EmacsConf - 2020\, and joined together around a\ncommon interest in Emacs and research - . Since then\, we have convened as\nthe Emacs Research Group for weekly m - eetings. During these meetings\, we\ntook notes collaboratively\, using a - ‘conflict-free replicated data type’\npackage (crdt.el)\; at the end of e - ach session\, we debriefed using a\ntemplate that we call a Project Action - Review (PAR). As as a\nmeta-review of our sessions\, every six weeks we - prepared a Causal\nLayered Analysis (CLA)\, which gave us a different pers - pective on what we\nhad done. We reflected further on our experiences and - methods\, linking\nour CLA to plans and design patterns. As a formal res - earch output\, we\ncontributed a write-up of these matters to a joint pape - r which we\npresented at the Pattern Languages of Programs Conference (PLo - P 2021).\nThe paper included an interactive workshop\, in which we explore - d roles\nin real-time problem solving and collaboration.\n\nIn our short t - alk we share information about these methods\, making a\ncase for other pe - ople getting together and creating their own small\nresearch communities s - imilar to ours. + conf.org/2021/talks/erg\n END:VEVENT BEGIN:VEVENT SUMMARY:One effective CS grad student workflow - Greg Coladonato @@ -487,19 +215,10 @@ UID:0f98a5bb-53ce-fb74-1003-0b1f320d414e URL:https://emacsconf.org/2021/talks/cs DTSTART:20211127T180100Z DTEND:20211127T181100Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Greg Coladonato":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/cs\n# One effective CS grad student workflow\nGreg Col - adonato\n\n\n\nWhen I was an undergrad\, I learned many things\, most of\n - which I forgot. In the time since then\, I've discovered Org Mode\, Org\nR - oam\, Org Noter\, Org Ref. PDF Tools\, and Anki. I would like to share\nmy - approach for capturing all the information that comes my way as a\nMS CS - student at Georgia Tech\, in the hopes that I can both get\nfeedback on wa - ys to improve the system I use\, as well as hopefully\ninspire others to b - uild workflows that make them more productive.\n\n\n\n# Outline\n\n- 5-1 - 0 minutes: Go through some typical workflows associated with being a grad - student\, using the packages mentioned in the abstract. + conf.org/2021/talks/cs\n END:VEVENT BEGIN:VEVENT SUMMARY:Using Org-Mode For Recording Continuous Professional Development - @@ -510,41 +229,10 @@ UID:43cc5db4-e26f-fb44-9aeb-b16c38d8cef3 URL:https://emacsconf.org/2021/talks/professional DTSTART:20211127T181400Z DTEND:20211127T182500Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Philip Beadling":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/professional\n# Using Org-Mode For Recording Continuou - s Professional Development\nPhilip Beadling\n\n\n\nI recently had the plea - sure of being audited for my CPD record with one\nof the large engineering - professional bodies. I decided to harness\norg-mode's TODO lists to reco - rd CPD items and my progress against them\ncompletely within Emacs. I als - o wanted the ability to export the data\nin a well presented\, compact for - mat for auditing submission.\n\nThe project was a success (I passed the au - dit) and the resulting system\nintegrates really well into my wider daily - Emacs workflow\, making future\nCPD recording seamless.\n\nThe talk will e - xplain how I tweaked and extended org-mode to get it to\nrecord the data I - wanted\, followed by a demo.\n\nA basic demo org file with embedded elisp - can be seen here:\n<https://raw.githubusercontent.com/falloutphil/Misc/ma - ster/cpd.org>\n\nA basic generated PDF from the basic demo is here:\n\n\nI have a much more involv - ed example I could also use for the demo.\n\nThe template contains a few e - xamples. Examples are Goals that are split\nup into Activities. All Activ - ities must have a Goal\, and within a Goal\nall activities must be complet - e for the Goal to be automatically set to\ncomplete.\n\nIt's basically lev - eraging Org Capture Templates to create custom Goals\nand Activities.\n\nO - n save or update these are then rendered into a table using Column View.\n - \nActivities are sorted by date they were completed on.\n\nThe Column View - is pre-configured to be exported to PDF in a condensed\nbut readable form - at for submission. It stays fairly readable even when\nthe pages get busy. - \n\nThe elisp required is all under the "Config" bullet and Emacs will ask - \nto execute it on opening the Org file. The elisp concerns itself with\nn - ice custom org capture functions and a few functions to ensure nice\nforma - tting on export\, etc.\n\n\n\n# Outline\n\n- 5-10 minutes:\n\nA quick wa - lkthrough of the setup and functions\, followed by a demo of how\nto add C - PD items\, and update them. Finally show generation of a PDF\ncontaining - all the items tabulated and ready for audit review. I\nestimate this at a - pprox 10 minutes. + conf.org/2021/talks/professional\n END:VEVENT BEGIN:VEVENT SUMMARY:Creating technical API documentation and presentations using org-ba @@ -555,23 +243,10 @@ UID:a10ce62e-6454-d784-21bb-f6a0488e883c URL:https://emacsconf.org/2021/talks/tech DTSTART:20211127T182700Z DTEND:20211127T183800Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Jan Ypma":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/tech\n# Creating technical API documentation and prese - ntations using org-babel\, restclient\, and org-treeslide\nJan Ypma\n\n\n\ - nThe emacs org-babel package is often mentioned in conjunction with\nliter - ate programming. The ability to mix code segments with prose\nindeed offer - s an intuitive way to augment semantic code pieces with\ntextual descripti - ons.\n\nIn recent projects\, I've started to turn to org-mode as the prima - ry\nformat to maintain technical documentation\, as well as slides for a\n - technical language course. By using org-babel to pull in "live" code\nfor - REST requests\, language examples\, and shell scripts\, one can be\nsure t - hat the documentation and slides are never out of date.\n\nThe session wil - l show how leverage org-babel\, restclient and\norg-treeslide to write and - present technical documentation with style.\n\n\n# Outline\n\n- Introduct - ion\n- Demo: Developer guide\n- Demo: REST API guide\n- Demo: Presentation - s\n- Used packages and configuration + conf.org/2021/talks/tech\n END:VEVENT BEGIN:VEVENT SUMMARY:Org as an executable format - Tom Gillespie @@ -581,36 +256,10 @@ UID:b092bc88-e74c-a9c4-611b-d47c99ef578c URL:https://emacsconf.org/2021/talks/exec DTSTART:20211127T184000Z DTEND:20211127T184800Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Tom Gillespie":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/exec\n# Org as an executable format\nTom Gillespie\n\n - \n\nOrg mode is known for its flexibility\, power\, and staggeringly diver - se\nnumber of workflows\, users\, and use cases.\n\nThis talk explores jus - t how far we can push the boundaries of the sane\nand sensible with regard - to Org workflows.\n\nIn particular it will discuss shebang blocks\, and e - lvs: two parts of a\ncomplete system for creating executable Org files.\n\ - nOrg syntax does not support shebang lines. However\, it turns out that\nO - rg syntax enables something even better —\; shebang blocks.\n\nOrg i - s also (supposedly) not an executable file format. However\, by\ncombinin - g a shebang block with a Org babel source block\, and eval\nlocal variable - s (elvs) Org becomes a multi-language executable format.\n\nIn this talk w - e introduce shebang blocks and elvs as a two part system\nthat transforms - Org files into executable documents that can run on any\nrecent version of - Emacs.\n\nThese ideas are implemented in\n<https://github.com/tgbugs/orgs - trap/blob/master/README.org> and\n<https://github.com/tgbugs/orgstrap/blob - /master/shebang.org>\, and\norgstrap.el is available as a package on MELPA - and can be installed\nvia M-x install-package orgstrap.\n\nThe talk will - open with a demo of how to create an executable Org file\nusing the orgstr - ap machinery.\n\nWe then discuss security considerations\, and show exampl - e use cases.\n\nFinally the talk will cover the details and development of - the\nportable shebang block for Org mode that works on a wide variety of\ - nsystems and shells\, and on the development of a formal specification\nan - d a reference implementation for using Org source blocks to\ntransform Org - files from plain text documents with a bit of markup\ninto self describin - g computational documents\, or interactive\napplications.\n\n\n\n# Outline - \n\n- 5-10 minutes:\n\nA demo of adding the orgstrap block and elvs\,\na - dding a shebang block\, and then running an org file. + conf.org/2021/talks/exec\n END:VEVENT BEGIN:VEVENT SUMMARY:The use of Org mode syntax outside of GNU/Emacs - Karl Voit @@ -620,23 +269,10 @@ UID:69763d57-be4e-7e74-509b-92e48a0e7ba6 URL:https://emacsconf.org/2021/talks/org-outside DTSTART:20211127T185100Z DTEND:20211127T190300Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Karl Voit":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/org-outside\n# The use of Org mode syntax outside of G - NU/Emacs\nKarl Voit\n\n\n\nWith the rising interest in Org mode\, the GNU/ - Emacs community gained\nmuch momentum in the last decade. Being a nicely d - esigned lightweight\nmarkup language\, Org mode does not only benefit user - s of GNU/Emacs.\nThere are many tools and services supporting Org mode syn - tax documents\nthat do have no direct connection to GNU/Emacs. I would lik - e to\nelaborate on the advantages on using Org mode syntax for arbitrary\n - text outside of GNU/Emacs for better typing usability and\ncollaboration t - asks.\n\n\n\n# Outline\n\n- 5-10 minutes: (brief description/outline)\n\ - nThis can only be a short teaser for the use of Org mode syntax without\nm - uch comparison to other lightweight markup languages. For this\naudience\, - I do think that this would be too short because most\nattendees might alr - eady have heard the rumors that Org mode is great\nor they have adapted Or - g mode in their workflows already. + conf.org/2021/talks/org-outside\n END:VEVENT BEGIN:VEVENT SUMMARY:Using Org-mode to teach programming - Daniel German @@ -646,28 +282,10 @@ UID:aed5e190-66a0-3dd4-e5eb-be09be94e6c3 URL:https://emacsconf.org/2021/talks/teach DTSTART:20211127T190400Z DTEND:20211127T192500Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Daniel German":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/teach\n# Using Org-mode to teach programming\nDaniel G - erman\n\n\n\nIn this presentation I will explain how to use org-mode effec - tively to\nprepare teaching materials\, and how to present them.\n\nFor th - e last 5 years I have been using org-mode to teach programming\nin differe - nt languages: C++\, SQL\, Ruby\, Python\, SML\nand Scheme. Org-mode has th - ree key advantages:\n\n1. it supports most programming languages with a c - ommon interface\,\n2. it is an interactive medium for delivering teaching - materials\; and\n3. it is an always-up-to-date format that does not need - to be exported in order to be published.\n\nI explain how I use org-mode - in my courses and how I combine org-mode\nnotes other tools such as github - org-mode to get\nalways up-to-date teaching materials that one can use fo - r both\nteaching and studying (see\n<https://github.com/dmgerman/csc116Mod - ernCplusplus/blob/master/lectures/l-01-1-intro/01_1_intro.org>\nfor an exa - mple).\n\nFinally\, I will discuss some important aspects to consider when - using\norg-mode for this purpose.\n\n\n\n# Outline\n\n20 minutes:\n\n- - Introduction\n- Quick demonstration\n- Workflow\n- Some Important co - nsiderations\n- Emacs configuration and how to get started\n\nI have cre - ate a git repository with examples and config files that is ready to use:\ - n<https://github.com/dmgerman/teachingProgOrg> + conf.org/2021/talks/teach\n END:VEVENT BEGIN:VEVENT SUMMARY:Managing a research workflow (bibliographies\, note-taking\, and ar @@ -678,26 +296,10 @@ UID:fd246cee-b5d6-7cc4-2b63-20e87bb7d750 URL:https://emacsconf.org/2021/talks/research DTSTART:20211127T192900Z DTEND:20211127T193400Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Ahmed Khaled":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/research\n# Managing a research workflow (bibliographi - es\, note-taking\, and arXiv)\nAhmed Khaled\n\n\n\nResearchers and knowled - ge workers have to read and discover new papers\,\nask questions about wha - t they read\, write notes and scratchwork\, and store\nmuch of this inform - ation for use in writing papers and/or code. Emacs allows\nus to do all of - this (and more) using simple text interfaces that integrate\nwell togethe - r. In this talk I will talk about the following:\n\na. Using elfeed and el - feed-score to read new papers from arXiv.\nb. Using org-ref to import arXi - v papers of interest into a local\nbibliography.\nc. Using Emacs hooks wit - h biber and rebiber in order to keep the local\n bibliography clean and - up-to-date with conference versions of papers.\nd. Using org-roam and org- - roam-bibtex to take linked\, searchable notes in\norg on research papers.\ - n\nThis text-based workflow allows for keeping everything accessible under - \nversion\ncontrol and avoids the platform lock-in of binary formats (e.g. - Mendeley). I\nwill share my Doom Emacs configuration for this workflow\, - but it is not\nlimited\nto Doom.\n\n\n\n# Outline\n\n- 5-10 minutes: I w - ill demo the packages I use in 5 minutes. + conf.org/2021/talks/research\n END:VEVENT BEGIN:VEVENT SUMMARY:Babel for academics - Asilata Bapat @@ -707,42 +309,10 @@ UID:db5821ed-fef4-4934-8fb3-87a0282714de URL:https://emacsconf.org/2021/talks/babel DTSTART:20211127T193800Z DTEND:20211127T194800Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Asilata Bapat":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/babel\n# Babel for academics\nAsilata Bapat\n\n\n\nPla - in org-mode is already an extremely powerful and\ncustomisable tool for ta - sk and time management\, note-taking\, calendar\nand agenda management\, a - nd much more. Babel takes org a step further\nby letting you write\, evalu - ate\, and export code in different languages\nfrom within a single file. I - n this talk\, I will highlight some\nfeatures of babel that I find excitin - g and extremely useful\,\nparticularly for an academic workflow.\n\nGettin - g started with babel can be intimidating\, but it's hard to stop\nusing it - once you start. As an academic\, I typically don't manage\nlarge coding p - rojects. My primary purpose is writing lecture notes\,\nassignments\, and - papers\, and managing related admin. Typically\, I want\nto try and automa - te the boring portions of my workflow without extra\noverhead. I also tend - to find various tasks easier in some programming\nlanguages and harder in - others\, and prefer to mix and match languages\nas the task dictates. Bab - el makes this process seamless.\n\nA basic use case is writing a document - in org-mode and exporting it to\nLaTeX or HTML. Org-mode even lets you wri - te multiple documents in a\nsingle org file\, which can be convenient. Bab - el lets you add all sorts\nof enhancements to the same file. For example\, - suppose we have a\nsingle org document with all the problem sets for a co - urse. Within\nthis single file\, we could now:\n\n- draw pictures in dit - aa\, graphviz\, or python instead of LaTeX\,\n- use python to do complex - calculations and then output the result as LaTeX\,\n- define skeletons - to quickly draw up assignment templates\,\n- toggle exporting of assignm - ents with or without solutions based on tags\,\n- locally change export - settings or run a post-export hook\,\n- automatically export to LaTeX af - ter saving\,\n- tangle code blocks from some or all of the languages to - external files.\n\nI will try to showcase features of babel that academics - could find\nhelpful\, by presenting some ways in which I have tried to us - e babel. I\nwould also like to be inspired by other people's babel workflo - ws!\n\n\n\n# Outline\n\n- 5-10 minutes: (brief description/outline)\n\nF - or a 5-10 minute presentation I will give a brief intro and present one or - two example files that heavily use babel. I will use these\nexamples to h - ighlight some of the features mentioned in the abstract. + conf.org/2021/talks/babel\n END:VEVENT BEGIN:VEVENT SUMMARY:Reproducible molecular graphics with Org-mode - Blaine Mooers @@ -752,44 +322,10 @@ UID:1fc4917c-aab4-1924-2983-e78f8bca6af9 URL:https://emacsconf.org/2021/talks/molecular DTSTART:20211127T195000Z DTEND:20211127T200100Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Blaine Mooers":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/molecular\n# Reproducible molecular graphics with Org- - mode\nBlaine Mooers\n\n\n\nResearch papers in structural biology should in - clude the code used to make\nthe images of molecules in the article in the - supplemental materials.\nSome structural bioinformaticists have started t - o include\ntheir computer code in the supplemental materials to allow read - ers\nto reproduce their analyses. However\, authors of papers reporting ne - w\nmolecular structures often overlook the inclusion of the code that make - s\nthe images of the molecules reported in their articles. Nonetheless\,\n - this aspect of reproducible research needs to become the standard practice - \nto improve the rigor of the science.\n\nIn a literate programming docume - nt\, the author interleaves blocks\nof explanatory prose between code bloc - ks that make the images of molecules.\nThe document allows the reader to r - eproduce the images in the manuscript by running the code.\nThe reader can - also explore the effect of altering the parameters in the\ncode. Org file - s are one alternative for making such literate programming\ndocuments.\n\n - We developed a **yasnippet** snippet library called **orgpymolpysnips** fo - r\nstructural biologists (<https://github.com/MooersLab/orgpymolpysnips>). - \nThis library facilitates the assembly of literate programming documents\ - nwith molecular images made by PyMOL. PyMOL is the most popular\nmolecular - graphics program for creating images for publication\; it has\nover 100\, - 000 users\, which is a lot of users in molecular biology. PyMOL\nhas been - used to make many of the images of biological molecules found\non the cove - rs of many Cell\, Nature\, and Science issues.\n\nWe used the **jupyter** - language in **org-babel** to send commands from\ncode blocks in Org files - to PyMOL's Python API. PyMOL returns the\nmolecular image to the output bl - ock below the code block. An Emacs\nuser can convert the Org file into a P - DF\, `tangle' the code blocks\ninto a script file\, and submit these for n - on-Emacs users. We describe\nthe content of the library and provide exampl - es of the running PyMOL\nfrom Org-mode documents.\n\n\n# Outline\n\n- 5- - 10 minutes: (brief description/outline)\n - Title slide\n - Stru - ctural Biolog Workflow in the Mooers Lab\n - Cover images made with P - yMOL\n\n - Why develop a snippet library for your field?\n - PyM - OL in Org: kernel specification\n - Creating a conda env and installi - ng PyMOL\n - Example code block in Org to make DSSR block model of tR - NA\n - Resulting image\n - Summary\n - Acknowledgements + conf.org/2021/talks/molecular\n END:VEVENT BEGIN:VEVENT SUMMARY:Budgeting\, Project Monitoring and Invoicing with Org Mode - Adolfo @@ -800,19 +336,10 @@ UID:c54c7930-51cc-5184-9dfb-5033e577b95e URL:https://emacsconf.org/2021/talks/project DTSTART:20211127T200300Z DTEND:20211127T201300Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Adolfo Villafiorita":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/project\n# Budgeting\, Project Monitoring and Invoicin - g with Org Mode\nAdolfo Villafiorita\n\n\n\nIn this talk I will present ho - w we use Org Mode at Shair.Tech for\nbudgeting\, project monitoring\, and - invoicing.\n\nWe are a small company and we are still tuning and improving - the\nprocess\, but with a bit of Emacs Lisp\, the functions Org Mode\npro - vides\, and reading here and there what other users do\, we\nimplemented a - n effective workflow we have been using for nearly a\nyear\, now\, and wit - h which we are very happy. Talk duration:\n\n–\;> 20 minutes seems t - o be right (15 talk + questions)\n–\;> I can also make in 10 minutes - \, by focusing the talk on\n budgeting (or monitoring) + conf.org/2021/talks/project\n END:VEVENT BEGIN:VEVENT SUMMARY:Finding Your (In)voice: Emacs for Invoicing - Bala Ramadurai @@ -822,25 +349,10 @@ UID:c9870e10-2600-85a4-24fb-793dfc51164e URL:https://emacsconf.org/2021/talks/invoice DTSTART:20211127T201600Z DTEND:20211127T202600Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Bala Ramadurai":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/invoice\n# Find Your (In)voice: Emacs for Invoicing\nB - ala Ramadurai\n\n\n\nYe Freelance warriors\, please lend me your I/O devic - es for 5 minutes.\n\nYour time is your money! Do you find it a pain to gen - erate an invoice\,\nrecord the details into your accounting software and k - eep track of\ntaxes and payments? You are not alone\, I found the whole in - voice\nthingy to be extremely painful.\n\nBut worry not\, Emacs comes to o - ur rescue.\n\nMy talk will give you a basic intro on how to use org mode\, - some embedded python code and file jugglery to generate stylistic and pro - fessional invoices.\n\nWhat you will learn during the session:\n\n- How - to track your freelance time using orgmode\n- How to create the basic in - frastructure for invoice generation\n- How to generate the invoice\n- - How to manage multiple clients\n- How to enter the finance details into - your accounting software\n- How to track invoice payments\n\nWe will use - the following packages:\n\n- Emacs+orgmode (duh?)\n- yasnippet\n- p - ython layer (I use spacemacs\, so whatever is the equivalent in your confi - g)\n- Some unnecessary Shakespearean references + conf.org/2021/talks/invoice\n END:VEVENT BEGIN:VEVENT SUMMARY:Productivity Dashboards with Emacs and Kindle - Mehmet Tekman @@ -850,50 +362,10 @@ UID:e4e995c0-6e06-8544-a8c3-5f9a06c856fb URL:https://emacsconf.org/2021/talks/dashboard DTSTART:20211127T202900Z DTEND:20211127T203900Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Mehmet Tekman":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/dashboard\n# Productivity Dashboards with Emacs and Ki - ndle\nMehmet Tekman\n\n\n\nSince 2008\, Amazon have released a new Kindle - device every year\,\nsupplanting each generation with a newer model that b - oasts highly\npromoted incremental features which greatly devalues the pri - ce of\ntheir older models. These forgotten models are sold on Ebay and\not - her secondhand websites at highly discount prices by owners who\ndo not se - e the true potential of these devices: Kindles are\nexcellent high contras - t low-refresh display rate E-Ink devices\,\nwith Wifi capability\, that ru - n embedded Linux in the\nbackground. Depending on the model\, an idle Kind - le can last weeks\nbefore needing a recharge. This makes them ideal as pas - sive image\ndevices that can be configured easily using a few shell\nscrip - ts. Indeed\, efforts have been made in dedicated hacker forums\nto expose - the Linux filesystem and to enable features such as\ncustom screensavers\, - SSH networking\, and more. By exploiting these\nfeatures\, and by careful - ly disabling the software/bloatware that\ncomes with the device\, these Ki - ndles have found new life as online\ndashboard devices which can fetch and - display information from the\ninternet at timely intervals.\n\nHere we de - scribe a tool to control multiple Kindle devices with a\nsingle org-mode/s - hell-based tool\, built initially to periodically\nserve updated Emacs Org - -Agenda views\, but later expanded to produce\nonline local weather report - s and work calendar\, Emacs calendars\n(calfw\, org-gcal)\, daily dietary - information (org-calories)\,\nOrg-Mode sparse TODO trees\, miscellaneous i - mage and text content\n(via imagemagick)\, small messages\, and much more. - \n\nIn this talk\, we show how to configure multiple Kindles with any\ndes - ired custom content\, following any daily/weekly schedule\, all\neasily ma - naged from Emacs within a single Org-Mode file.\n\n\n\n# Outline\n\n- 5- - 10 minutes:\n\n 1-3 mins\n Talk about repurposing Kindles:\n\n - - Cheap second-hand wifi device\, hackable\n - Low-powered\, lo - ng battery life\, low refresh rate –\; perfect\n for a dashbo - ard\n - Timely updated Org-Mode Agendas anyone?\n - Referenc - e to inspired projects (kindle-dashboard)\n\n 2-3 mins\n Gener - ate content\n\n - A static text+picture image easily generated with i - magemagick\n wrapper\n - An image of a sparse tree of org-mode - TODO file\n - An image of another emacs view (e.g. Calfw\, or org-ca - lories)\n - Show post-processing for optimizing image for Kindles\n\n - 1-2 mins\n Configuration in a single org-mode file\n\n - - Defining Machines\n - Defining Commands to generate content\n - - Defining Schedules to run Commands on multiple Machines at\n speci - fic points in the day\n\n 1-2 mins\n Export and Run:\n\n - - Show exported shell configs and generated cronjobs\n - Witness mult - iple Kindles producing desired content with wakeup\n timers + conf.org/2021/talks/dashboard\n END:VEVENT BEGIN:VEVENT SUMMARY:Emacs with Nyxt: extend your editor with the power of a Lisp browse @@ -904,25 +376,10 @@ UID:33776e08-e815-db94-971b-a151236e11be URL:https://emacsconf.org/2021/talks/nyxt DTSTART:20211127T204200Z DTEND:20211127T205200Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Andrea":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/nyxt\n# Emacs with Nyxt: extend your editor with the p - ower of a Lisp browser\nAndrea mailto:andrea-dev@hotmail.com - pronouns: h - e/him -- https://ag91.github.io\n\n\n\nIn 2021 browsers are essential if y - ou use a computer. Even if Emacs\nusers love text as a format\, they may n - eed to shop and video call from\ntime to time (even more so in a pandemic! - ). Some of us modified their\nbrowsers to at least have the same keybindin - gs as our editor of\nchoice. What if I told you there is an Emacsy browser - in the making?\nWhat if you could "ace-jump" within a web page? What if y - ou could run\na REPL to extend your browser while browsing? What if you co - uld record\nmacros?! The browser exists: its name is Nyxt!\n\nIn this talk - I will share why it has great potential\, how you can\nintegrate it with - Emacs\, and how you can migrate your Emacs mastery to\nthe web!\n\nIf you - were wishing for a Lispy and Emacsy browser\, you should not\nmiss this ta - lk!\n\nYou can learn more about this at: <https://github.com/ag91/emacs-wi - th-nyxt>\n\n\n\n# Outline\n\n- 5-10 minutes: quick demo of running Nyxt - from Emacs and a little explanation of the code necessary for integration + conf.org/2021/talks/nyxt\n END:VEVENT BEGIN:VEVENT SUMMARY:On the design of text editors - Nicolas P. Rougier @@ -932,34 +389,10 @@ UID:86d4470a-8d19-7bd4-0c53-6aba1b49baef URL:https://emacsconf.org/2021/talks/design DTSTART:20211127T205500Z DTEND:20211127T210500Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Nicolas P. Rougier":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/design\n# On the design of text editors\nNicolas P. Ro - ugier\n\n\n\nText editors are written by and for developers. They come\nw - ith a large set of default and implicit choices in terms of layout\,\ntypo - graphy\, colorization and interaction that hardly change from one\neditor - to the other. It is not clear if these implicit choices derive\nfrom the i - gnorance of alternatives or if they derive from developers'\nhabits\, repr - oducing what they are used to. Durint this talk\, I will\ncharacterize the - se implicit choices and illustrate what are some\nalternatives using GNU E - macs.\n\n# Outline\n\n1. Review of a "modern" code editor (5mn)\n2. Introd - uction of an alternative using Emacs (5mn)\n\n## Links from the slides:\n\ - n* [Elegant Emacs](https://github.com/rougier/elegant-emacs) (https://gith - ub.com/rougier/elegant-emacs)\n* [On the Design of Text Editors](https://a - rxiv.org/abs/2008.06030) (https://arxiv.org/abs/2008.06030)\n* [N Λ N O Em - acs](https://github.com/rougier/nano-emacs) (https://github.com/rougier/na - no-emacs)\n* [svg-lib (ELPA)](https://elpa.gnu.org/packages/svg-lib.html) - (https://elpa.gnu.org/packages/svg-lib.html)\n* [nano-theme (ELPA)](https: - //elpa.gnu.org/packages/nano-theme.html) (https://elpa.gnu.org/packages/na - no-theme.html)\n* [nano-modeline (ELPA)](https://elpa.gnu.org/packages/nan - o-modeline.html) (https://elpa.gnu.org/packages/nano-modeline.html)\n* [na - no-agenda (ELPA)](https://elpa.gnu.org/packages/nano-agenda.html) (https:/ - /elpa.gnu.org/packages/nano-agenda.html)\n\n## Contact information\n* Cont - act [nicolas.rougier@inria.fr](mailto:nicolas.rougier@inria.fr)\n* Follow - my work at [github.com/rougier](https://github.com/rougier)\n* Support my - work at [github.com/sponsors/rougier](https://github.com/sponsors/rougier) - or [en.liberapay.com/rougier/](https://en.liberapay.com/rougier/) + conf.org/2021/talks/design\n END:VEVENT BEGIN:VEVENT SUMMARY:Emacs development updates - John Wiegley @@ -969,10 +402,10 @@ UID:59e4daca-1e46-9054-9573-9c91966d6987 URL:https://emacsconf.org/2021/talks/dev-update DTSTART:20211127T210900Z DTEND:20211127T211700Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="John Wiegley":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/dev-update\n# Emacs development updates\nJohn Wiegley + conf.org/2021/talks/dev-update\n END:VEVENT BEGIN:VEVENT SUMMARY:How Emacs made me appreciate software freedom - Protesilaos Stavrou @@ -982,34 +415,10 @@ UID:48a8580f-52ce-cc84-6a23-1eddf720ae02 URL:https://emacsconf.org/2021/talks/freedom DTSTART:20211127T212000Z DTEND:20211127T215800Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Protesilaos Stavrou":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/freedom\n# How Emacs made me appreciate software freed - om\nProtesilaos Stavrou\n\n\n\nThe theme will be "how Emacs empowered my s - oftware freedom".\nI will outline the key moments in my transition to a GN - U/Linux operating\nsystem and mark those which eventually contributed towa - rds me becoming\nan Emacs user\, maintainer of a—\;dare I say— - \;popular package\, and\ncontributor to upstream Emacs (among others). By - alluding to personal\nexperiences\, I will draw generalisable insights an - d connect them to what\nI believe are irreducible qualities of Emacs qua s - oftware and Emacs as a\ncommunity of like-minded people. The talk will be - theoretical in\nnature: there won't be any code-related demonstration nor - technical\nreferences that only people with a background in computer scie - nce would\nlikely recognise. Personal anecdotes shall be tangential to th - e point\nand considered as ancillary to the thesis of what Emacs represent - s from\nthe standpoint of software freedom and user empowerment. The\npre - sentation is intended for a general audience that is interested in\nGNU so - ftware in general and Emacs in particular. My formal educational\nbackgro - und as a social scientist (i.e. not a programmer) and later as a\nphilosop - her informs my approach to this topic.\n\nThe presentation shall be 40 min - utes long. Its text will be in essay\nform and shall be supplied as compl - ementary material to the video. The\nnotation will be in Org mode. I can - not provide an outline in advance\,\nas it will most likely not be consist - ent with the actual presentation.\nIf\, however\, this is absolutely requi - red for administrative purposes I\nshall furnish one regardless with the p - roviso that I am in no way bound\nby it and thus reserve the right to modi - fy it ahead of the main event. + conf.org/2021/talks/freedom\n END:VEVENT BEGIN:VEVENT SUMMARY:Closing remarks day 1 @@ -1019,9 +428,9 @@ UID:5287b003-f368-36c4-4f9b-8135734cad39 URL:https://emacsconf.org/2021/talks/day1-close DTSTART:20211127T220000Z DTEND:20211127T220500Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/day1-close\n# Closing remarks day 1 + conf.org/2021/talks/day1-close\n END:VEVENT BEGIN:VEVENT SUMMARY:Opening remarks day 2 @@ -1031,9 +440,9 @@ UID:d877a57a-14cf-a194-99c3-a344ecb24acc URL:https://emacsconf.org/2021/talks/day2-open DTSTART:20211128T140000Z DTEND:20211128T140500Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/day2-open\n# Opening remarks day 2 + conf.org/2021/talks/day2-open\n END:VEVENT BEGIN:VEVENT SUMMARY:How to write faster Emacs Lisp - Dmitry Gutov @@ -1043,18 +452,10 @@ UID:35d1d9e4-dfdf-f254-6aab-7a466fbfaf09 URL:https://emacsconf.org/2021/talks/faster DTSTART:20211128T140500Z DTEND:20211128T142500Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Dmitry Gutov":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/faster\n# How to write faster Emacs Lisp\nDmitry Gutov - \n\n\n\n- Before optimizing\, benchmark first.\n- Different benchmarki - ng approaches.\n- Live evaluation\, step-debugging\, measuring from a de - bugger breakpoint.\n- How to determine if a function is expensive. How t - o pick one from\n competing alternatives (cl-lib\, seq\, dash\, lean co - re).\n- Print-benchmarking.\n- Byte-compiled code can give a very diff - erent picture\, changing where\n the bottleneck is. How to quickly load - a byte-compiled version.\n- Steps taken to speed up the Xref package re - cently. + conf.org/2021/talks/faster\n END:VEVENT BEGIN:VEVENT SUMMARY:Tree-edit: Structural editing for Java\, Python\, C\, and beyond! - @@ -1065,33 +466,10 @@ UID:599ef3fa-4c73-6c94-4953-75bbc7830681 URL:https://emacsconf.org/2021/talks/structural DTSTART:20211128T143000Z DTEND:20211128T144100Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Ethan Leba":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/structural\n# Tree-edit: Structural editing for Java\, - Python\, C\, and beyond!\nEthan Leba\n\n\n\nIn this talk\, I'll discuss a - vision for how writing code could be\, where the\nediting operations map - directly to the primitives of the language itself -- and\nmy humble attemp - t of implementing this vision. _tree-edit_ seeks to provides a\nstructural - editing plugin supporting conceivably any language with a tree-sitter\npa - rser.\n\n**Structural editing does not have to be relegated to lisps or ni - che DSLs.**\n\nI liken the state of code editing today to writing assembly - . The reason why\npeople like Python more than assembly is that for most p - urposes\, the building\nblocks of the language are mismatched with our tho - ught process. We don't think\nin terms of registers and addresses\, we thi - nk in terms of variables\, functions\,\netc. So when we write and edit cod - e\, why do we edit in terms of deleting\,\ninserting\, replacing character - s –\; not wrapping\, inserting\, raising\,\ndeleting expressions and - statements?\n\nI'll also discuss the implementation of tree-edit\, which - uses a novel\ncombination of the fantastic\n[tree-sitter](https://github.c - om/emacs-tree-sitter/elisp-tree-sitter) parser\nwith an embedded logic pro - gramming DSL ([miniKanren](http://minikanren.org/)\,\nusing elisp port [re - azon](https://github.com/nickdrozd/reazon)) to power it's\nsyntax tree gen - eration.\n\nCheck out the GitHub repo [here](https://github.com/ethan-leba - /tree-edit)!\n\n# Outline\n\n- Discuss motivation - (Why should I care?)\n- Demonstrate tree-edit ( - Live-coding with tree-edit)\n- Demonstrate tree-edit syntax tree generat - or (Elevator pitch on miniKanren) + conf.org/2021/talks/structural\n END:VEVENT BEGIN:VEVENT SUMMARY:Self-Describing Smart DSL's: The Next Magits - Psionic @@ -1101,28 +479,10 @@ UID:29d45a6f-9425-f5a4-bd23-297292e4ab7a URL:https://emacsconf.org/2021/talks/dsl DTSTART:20211128T144300Z DTEND:20211128T150300Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Psionic":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/dsl\n# Self-Describing Smart DSL's: The Next Magits\nP - sionic\n\n\n\nWhen we begin programming\, the promise is to automate away - repetitive\ntasks in life. As those program's capability grows\, we begin - to need\nconfiguration UI's. We can start with a CLI\, but as any CLI gr - ows\, we\nrun into the following issues:\n\n- As options pile up\, the i - ntuition of simplicity is lost in helps and\nmanpages\n\n- Stateless ope - ration has no idea what to do next and loses terseness\n- Frequent dispatc - h of commands to interrogate state required for the\noperator to decide wh - at action to perform\n\n- Composition compounds with all of these issues - \n\nMagit has the UI trifecta of being terse\, intuitive\, and intelligent - .\nMagit's UI input library\, Transient\, is a standalone package for\ndev - eloping more killer UI's\, and not just for CLI applications\, but\nalso f - or server applications\, Emacs applications\, and Emacs itself.\n\nWhile T - ransient's potential is to create the most highly productive\nUI's short o - f thought control\, going beyond simple command dispatchers\nrequires a de - eper dive. When we think like constructing a DSL for the\ntask and using - transient to input that DSL\, we get an intelligent\,\nself-describing mod - al programming system.\n\n\n# Outline\n\n- Updates to Transient documenta - tion and demos of API examples\n- Wrapping a custom CLI tool in Transient + conf.org/2021/talks/dsl\n END:VEVENT BEGIN:VEVENT SUMMARY:"Yak-shaving to a UI framework" (/"Help! I accidentally yak-shaved @@ -1134,24 +494,10 @@ UID:8f62e571-91da-bd14-e7c3-b445c7b19d23 URL:https://emacsconf.org/2021/talks/ui DTSTART:20211128T150600Z DTEND:20211128T151600Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Erik Anderson":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/ui\n# "Yak-shaving to a UI framework" (/"Help! I accid - entally yak-shaved my way to writing a UI framework because overlays were - slow")\nErik Anderson\n\n\n\nTui.el is a textual User Interface (UI) frame - work for Emacs Lisp\nmodeled after the popular JavaScript 'React' framewor - k. This package\nimplements React Component API's with the goal of simpli - fying\ndevelopment of interactive UI's for all Emacs users- regardless of\ - ntheir prior experience with React or web programming. Components\nprovid - e a useful functional unit for constructing complex interfaces\ndeclarativ - ely and also eliminate much of the burden associated with\nupdating textua - l content as application state changes. This talk will\ncover use of the - tui.el API and its operation in a textual environment\nby implementing som - e basic UI's.\n\n\n\n# Outline\n\n- 5-10 minutes:\n - Problem space - : UI implementation complexity.\n - API introduction: Displaying cont - ent\, Components.\n - Visual taste of dashboards and applications bui - lt with tui. + conf.org/2021/talks/ui\n END:VEVENT BEGIN:VEVENT SUMMARY:Extending Emacs in Rust with Dynamic Modules - Tuấn-Anh Nguyễn @@ -1161,19 +507,10 @@ UID:b073d391-6c37-6bf4-7afb-47edc79631a9 URL:https://emacsconf.org/2021/talks/rust DTSTART:20211128T151900Z DTEND:20211128T153900Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Tuấn-Anh Nguyễn":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/rust\n# Extending Emacs in Rust with Dynamic Modules\n - Tuấn-Anh Nguyễn\n\n\n\nDynamic module support has been available since Ema - cs 25. It can be\nused to extend Emacs with native libraries\, for perform - ance\,\nOS-specific features\, or other functionalities that would take a - lot\nof time to re-implement in Lisp. The officially supported language is - \nC\, which is tedious and error-prone to use. This talk discusses a\n**sa - fe** alternative that is also a lot **more convenient**: writing these\ndy - namic modules in Rust.\n\n\n\n# Outline\n\n- Walking through creating **a - simple dynamic module** in\n Rust\, including setting up CI.\n- Going - through and explaining the **available APIs**. + conf.org/2021/talks/rust\n END:VEVENT BEGIN:VEVENT SUMMARY:Emacs Application Framework: A 2021 Update - Matthew Zeng @@ -1183,15 +520,10 @@ UID:e7981936-6d72-93d4-8783-5ac64a0ae5bb URL:https://emacsconf.org/2021/talks/eaf DTSTART:20211128T154400Z DTEND:20211128T155400Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Matthew Zeng":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/eaf\n# Emacs Application Framework: A 2021 Update\nMat - thew Zeng\n\n\n\nEmacs Application Framework (EAF) is a customizable and e - xtensible GUI\napplication framework that extends Emacs graphical capabili - ties using\nPyQt5. There are many new but important updates since EmacsCon - f2020\nlast year\, this talk will briefly go over them.\n\n\n\n# Outline\n - \n- 5-10 minutes: (brief description/outline) + conf.org/2021/talks/eaf\n END:VEVENT BEGIN:VEVENT SUMMARY:Extending the "model" of Emacs to other applications - Laszlo Krajn @@ -1202,55 +534,10 @@ UID:5e1baaaf-56a3-b5b4-31cb-5437cf465cf9 URL:https://emacsconf.org/2021/talks/model DTSTART:20211128T155800Z DTEND:20211128T160800Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Laszlo Krajnikovszkij":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/model\n# Extending the "model" of Emacs to other appli - cations\nLaszlo Krajnikovszkij\n\n\n\nEmacs is a great operating environme - nt in a sense that it provides consistency\nacross different tools and app - lications within the Emacs ecosystem\, as well as\nexternal apps that can - be integrated into it. It is also the most truly\nmalleable environment\, - each element of which can be adjusted or extended\,\ntherefore providing t - he user with more power and freedom in personal computing.\nEmacs definite - ly can be considered one of greatest software products in\nexistence.\n\nA - s a non-programmer\, having had the chance to stumble upon Emacs a couple - of\nyears ago\, the only regret to have is that it didn't happen earlier. - The definite\nkiller feature of Emacs - Org-mode\, is what draws many of t - he less technical\nfolks to join the party and gradually start to use Emac - s for writing documents\,\nwhether personal or work related\, manage tasks - \, emails and potentially everything\nelse. The learning curve and differe - nce in approach\, however\, leaves some\npotential users too scared of the - arcane interface even with all it's quirks and\nfeatures because it requi - res at least some technical skills to understand and\nuse properly\, and d - oes not have an easy way to connect with external tools that\nmost people - are forced to use for work.\n\nThis talk proposes some ideas about how the - model of Emacs\, it's focus on\nconsistency\, extensibility\, as well as - it's powerful interaction model can be\ncarried over to make modern interf - aces\, whether desktop or web applications\,\nthat would be designed with - a goal of reflecting the spirit of Emacs in terms of\nthe aforementioned f - eatures it possesses\, and therefore enhance the capabilities\nof the Emac - s\, while at the same time utilizing it as a backend for\ntext-processing - and editing to a large extent. It would be really great to have\na persona - l web-interface for using modern task management tools\, chats\, emails\na - nd such\, but from a UI defined by the user. The goal is to use it on a de - sktop\nor mobile\, locally or self-hosted on a server\, with support for t - ouch and\ngesture-based workflows\, while preserving the Emacs philosophy - and allowing to\nseamlessly switch between Emacs and its web extension\n\n - The proposed solution is to integrate more of the modern tools with Emacs\ - ,\nutilize Org-mode as a way to define application-specific parameters for - these\ntools through Org properties\, and then utilize these parameters f - or making a\nmodern local frontend that would enhance Emacs UI while allow - ing to use external\ntools in a more personal and freedom respecting way ( - making the originals\nobsolete over time). The talk serves the purpose of - inviting community members to\na discussion about how Emacs can become mor - e modern\, more approachable by people\nwho don't possess the neccessarry - technical skills to adjust it themselves\, but\nare keen to learn it\, and - potentially how to attract more users to greater\nproductivity\, computer - literacy and the ideas of free software.\n\n\n\n# Outline\n\n- 5-10 min - utes\n - Introduction\n - Issues with most modern tools for work - \n - Issues with Emacs as a tool for work\n - In search for a hy - brid approach\n - User controlled web-apps\n - Opinions encourag - ed\n - Contacts + conf.org/2021/talks/model\n END:VEVENT BEGIN:VEVENT SUMMARY:Don't write that package! or: How I learned to stop worrying and lo @@ -1261,28 +548,10 @@ UID:4cd6de26-cf48-95c4-9d3b-28895a43ec53 URL:https://emacsconf.org/2021/talks/devel DTSTART:20211128T161100Z DTEND:20211128T163100Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Stefan Kangas":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/devel\n# Don't write that package! or: How I learned t - o stop worrying and love emacs-devel\nStefan Kangas\n\n\n\nWe need a succe - ssful Emacs on this planet. This means that we need an\nexcellent out-of- - the-box experience -- one that just works\, but that you\ncan still hack a - nd customize. There is so much great experimentation\nand work going on o - ut there in the wider Emacs community\, but we would\nbe even better off i - f more of that could go into Emacs itself.\n\nEmacs' greatest strength is - unfortunately sometimes also its greatest\nweakness: it is *too* hackable. - \n\nOn occasion\, people out there add stuff to their Init file to fix thi - s\nor that annoyance\, or even bug. The more ambitious might go on to\npa - ckage up such fixes: "Hey\, 'foo-mode' doesn't have support for\n'bookmark - -set'\, let's write a package!" I am here to suggest that you\nshould not - do that.\n\nYou should submit a patch to Emacs! Maybe more people have t - hat same\nproblem or annoyance\, and would benefit from your solution?\n\n - It is sometimes perceived as hard to contribute to Emacs core. I want\nto - encourage more people to get involved\, and show that the barrier to\nent - ry is really not that high. If I can do it\, you can do it too!\n\nSo sho - uld you really write that package\, or should you stop worrying and\nlearn - to love emacs-devel? Listen to my talk to find out more! + conf.org/2021/talks/devel\n END:VEVENT BEGIN:VEVENT SUMMARY:Turbo Bindat - Stefan Monnier @@ -1292,20 +561,10 @@ UID:49a35f05-b71f-1d14-2343-a6638bec0d08 URL:https://emacsconf.org/2021/talks/bindat DTSTART:20211128T163600Z DTEND:20211128T170600Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Stefan Monnier":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/bindat\n# Turbo Bindat\nStefan Monnier\n\n\n\n\n# Tabl - e of Contents\n\n\n\nBindat is an ELisp library to help manipulate binary - data. This is a\nniche library that is used by packages such as Websocket\ - , EMMS\, and\ncpio-mode. Its implementation was repeatedly caught harassin - g hapless\nkitten while at the same time providing poor service slowly. Fo - r\nEmacs-28\, Bindat was rewritten so as to make it more efficient and\nfl - exible while respecting the kitten. In this presentation I intent to\nshow - how we saved those. Not recommended for birds.\n\n- ~20 minutes:\n 5 - min: Intro and presentation of Bindat\n 5 min: Showcase some of its pr - oblems\n 5 min: Present the new design\n 5 min: Examples of what can - be done with it + conf.org/2021/talks/bindat\n END:VEVENT BEGIN:VEVENT SUMMARY:Emacs Lisp native compiler\, current status and future developments @@ -1316,20 +575,10 @@ UID:1ddbe380-b4f3-2b84-3cc3-9e799536db8e URL:https://emacsconf.org/2021/talks/native DTSTART:20211128T174000Z DTEND:20211128T182000Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Andrea Corallo":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/native\n# Emacs Lisp native compiler\, current status - and future developments\nAndrea Corallo\n\n\n\nEmacs Lisp (Elisp) is the L - isp dialect used by the Emacs text editor\nfamily. GNU Emacs is tradition - ally capable of executing Elisp code\neither interpreted or byte-interpret - ed after it has been compiled to\nbyte-code.\n\nIn this talk I'll discuss - the Emacs Lisp native compiler. This feature\nrecently merged into the ma - in Emacs development line allow for\nautomatically compiling and executing - Elisp as native code.\n\nDuring the presentation I'll touch on:\n\n- de - sign goals\n- compiler and runtime design and implementation\n- perfor - mance implications\n- upstream process\n- area of improvements and fut - ure developments\n\nFormat: 40 minutes + conf.org/2021/talks/native\n END:VEVENT BEGIN:VEVENT SUMMARY:Old McCarthy Had a Form - Ian Eure @@ -1339,18 +588,10 @@ UID:5947c3e9-93c1-1014-7ffb-aa0e0097e3e4 URL:https://emacsconf.org/2021/talks/form DTSTART:20211128T182700Z DTEND:20211128T183700Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Ian Eure":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/form\n# Old McCarthy Had a Form\nIan Eure\n\n\n\nMost - practical languages are multi-paradigm\, offering several\nabstractions fo - r the programmer. But did you know that Emacs Lisp\ncomes with a powerful - system for object-oriented programming? Join me\nfor a discussion of EIEI - O\, and learn how it can help you write more\nmodular\, flexible Emacs Lis - p.\n\n\n\n# Outline\n\n- 5-10 minutes: (brief description/outline)\n - - What is CLOS/EIEIO?\n - Why would I want OOP in Emacs Lisp?\n - - How is the CLOS object model different from C++/Java/.NET?\n - Fu - rther reading + conf.org/2021/talks/form\n END:VEVENT BEGIN:VEVENT SUMMARY:Test blocks - Eduardo Ochs @@ -1360,37 +601,10 @@ UID:5e162d34-ea19-8544-b693-dd6da0e885cd URL:https://emacsconf.org/2021/talks/test DTSTART:20211128T184100Z DTEND:20211128T184600Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Eduardo Ochs":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/test\n# Test blocks\nEduardo Ochs\n\n\n\nIn this prese - ntation I will show an idea that feels completely obvious\nonce we see it\ - , but that only occured to me after after using Emacs\nand eev as my main - interface to the computer for more than 20 years.\nTake any interpreted la - nguage that supports multi-line comments\, and\nwhose interpreter can be r - un in an Emacs buffer - for example Lua\,\nHaskell\, Python\, or Julia\; l - et's say just "Lua" from here on for\nsimplicity. So: suppose that we have - a Lua script that we wrote\, that\nis called "foo.lua" and that defines l - ots of functions and defines the\nclasses Bar and Bletch. We can put after - the definition of the class\nBar a multi-line comment that contains an ee - pitch block that when\nexecuted starts a Lua interpreter\, loads the scrip - t foo.lua (by\nrunning 'dofile "foo.lua"')\, and then has several tests fo - r that class\nand its methods\; and we can put another block with tests li - ke that\nafter the class Bletch\, and other blocks after some functions. E - epitch\nallows sending these tests line by line to the Lua interpreter by\ - ntyping <f8\\> on each line that we want to send\, and this lets us create - \ntests that are very easy to understand even without writing comments\;\n - this gives us a very quick way to document code by executable tests\,\ntha - t is super-great for experimental code that is still going to\nchange a lo - t before running the risk of being read by other people.\n\nThese multi-li - ne comments with eepitch blocks that run an interpreter\nand make it load - the current file are called "test blocks". The\ncommand \\`M-x eeit' inser - ts a test block at point\, using the major mode\nto decide the right synta - x to use for the multi-line comments and for\nthe "dofile". We can configu - re the syntax of the test blocks for the\ncurrent major mode by running \\ - `M-x find-eeit-links'\; this can also be\nused to add support for test blo - cks to more languages (or\, more\nprecisely: to more major modes).\n\nEdua - rdo Ochs <http://angg.twu.net/emacsconf2021.html> + conf.org/2021/talks/test\n END:VEVENT BEGIN:VEVENT SUMMARY:Let's talk about bug trackers - Bastien Guerry @@ -1400,14 +614,10 @@ UID:51023225-018f-cf24-9d73-3c267907c13e URL:https://emacsconf.org/2021/talks/bug DTSTART:20211128T184900Z DTEND:20211128T190900Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Bastien Guerry":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/bug\n# Let's talk about bug trackers\nBastien Guerry\n - \n\n\nFor 17 years\, the Org developers didn't use a bug tracker\,\nshamel - essly failing the Joel Spolsky test. Why was it "good enough"?\nWhy was i - t wrong? Why did we move to Woof!? Why Woof! is not a bug\ntracker?\n\n- - 20 minutes + conf.org/2021/talks/bug\n END:VEVENT BEGIN:VEVENT SUMMARY:Perso-Arabic Input Methods And Making More Emacs Apps BIDI Aware - @@ -1418,65 +628,10 @@ UID:1407591a-29fd-3f64-1beb-01dea6e9d7d2 URL:https://emacsconf.org/2021/talks/bidi DTSTART:20211128T191600Z DTEND:20211128T193600Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Mohsen BANAN":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/bidi\n# Perso-Arabic Input Methods And BIDI Aware Apps - \nMohsen BANAN -- محسن بنان\n\n\n\nEmacs is a multilingual user environme - nt. A true multilingual editor must\nsupport bidirectionality and shaping - of characters. Perso-Arabic scripts require\nboth of these features.\n\nSt - arting with Emacs 24\, full native bidi\n(bidirectional) support became av - ailable. For\nmany years prior to that Unicode support was\navailable and - by around year 2000\, reasonable\nopen-source shaping libraries were also - available.\n\nWith these in place at around 2012\, I developed\ntwo Persi - an input methods for emacs. These input\nmethods or variations of them can - also be used for\nArabic and other Perso-Arabic scripts.\n\nWith all of t - hese in place\, Emacs has now become\nthe ne plus ultra Libre-Halaal and C - onvivial usage\nenvironment for Perso-Arabic users.\n\nSince emacs comes l - oaded with everything (Gnus\nfor email\, Bbdb for address books\, XeLaTeX - modes\nfor typesetting\, org-mode for organization\, spell\ncheckers\, com - pletion systems\, calendar\, etc.)\, all basic\ncomputing and communicatio - n needs of Perso-Arabic\nusers can be addressed in one place and\ncohesive - ly.\n\nIn this talk I will demonstrate what a wonderful\nenvironment that - can be.\n\nMy talk will be in two parts.\n\nIn Part 1\, I cover Persian in - put methods. With an emphasis on "Banan\nMulti-Character (Reverse) Transli - teration Persian Input Method". The\nsoftware is part of base emacs distri - bution. Full documentation is available\nat:\n\n Persian Input M - ethods\n For Emacs And More Broadly Speaking\n شیوهها - یِ درج به فارسی\n <http://mohsen.1.banan.byname.net/PLPC/120036 - >\n\nIn Part 2\, I'll demonstrate that Emacs is far more than an editor. E - macs can be\na complete Perso-Arabic usage environment. I will also cover - the ramifications\nof bidi on existing emacs applications\, including:\n\n - - Spell Checking\, Dictionaries And Completion Frameworks:\n - Existi - ng emacs facilities can be extended to cover Perso-Arabic.\n\n- Gnus:\n - - Perso-Arabic rich email sending in HTML.\n - Ramifications of - bidi on from:\, to: and subject: lines.\n\n- Bbdb: Ramifications of bidi - on display and completion.\n\n- Calendar:\n - Ramifications of bid - i on display.\n - Use of Persian text for Persian (solar) calendar.\n - - Use of Arabic text for Muslem (lunar) calendar.\n\n- AUCTeX: Pe - rsian typesetting with XeLaTeX\n - Option of having right-to-left Pe - rso-Arabic aliases for all latex commands.\n\nReferences:\n\n - Persian - Input Methods:\n <http://mohsen.1.banan.byname.net/PLPC/120036>\n - <http://www.persoarabic.org/PLPC/120036> -- Persian Input Methods Acces - s Page\n <http://www.persoarabic.org> -- Various Perso-Arabic resourc - es\n <http://www.freeprotocols.org/Repub/fpf-isiri-6219> -- Re-Public - ation Of\n Persian Information Interchange and Display Mechanism\ - , using Unicode\n <https://github.com/bx-blee/persian-input-method> - - - Git repo for\n persian.el -- Quail package for inputting Persia - n/Farsi keyboards\n\n - BIDI:\n <http://www.unicode.org/reports/tr - 9/> -- Annex #9 of the Unicode standard\n <https://www.gnu.org/softwa - re/emacs/manual/html_node/elisp/Bidirectional-Display.html>\n Ema - cs Bidirectional Display\n\n - Blee and Persian-Blee:\n <https://g - ithub.com/bx-blee/env2> -- Very messy work-in-progress git repo for:\n - Blee: By* Libre-Halaal Emacs Environment\n <http://www.by-star. - net> -- A Moral Alternative To The Proprietary American Digital Ecosystem\ - n <http://mohsen.1.banan.byname.net/PLPC/120033> --\n Natu - re of Polyexistentials:\n Basis for Abolishment of The Western - Intellectual Property Rights Regime\n <http://mohsen.1.banan.byname.n - et/PLPC/120039> -- Defining The Libre-Halaal Label\n\n - Mohsen BANAN - - - محسن بنان:\n <http://mohsen.1.banan.byname.net/> -- Globish\n - <http://mohsen.1.banan.byname.net/persian> -- Farsi\n <http://mohsen. - 1.banan.byname.net/french> -- French + conf.org/2021/talks/bidi\n END:VEVENT BEGIN:VEVENT SUMMARY:Moldable Emacs\, a step towards sustainable software - Andrea @@ -1486,28 +641,10 @@ UID:3364aedb-a496-5c64-5383-b0080afa6d7b URL:https://emacsconf.org/2021/talks/mold DTSTART:20211128T194100Z DTEND:20211128T195100Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Andrea":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/mold\n# Moldable Emacs\, a step towards sustainable so - ftware\nAndrea mailto:andrea-dev@hotmail.com - pronouns: he/him -- https:/ - /ag91.github.io\n\n\n\nWe could learn about things better. Mountains of kn - owledge hide in\nplaces we cannot access or use. The more we write down\, - the more it\ntakes to find and understand things we find useful.\n\nKnowle - dge (web\, software\, books) keeps growing faster and faster! This\nis not - sustainable: we cannot keep up with it! What if we repeat the\nerror of s - omebody else\, only because it would take too much reading to\nknow? What - if that knowledge is in some code we work with everyday?\n\nMoldable devel - opment is a paradigm shift that attempts to solve this\nproblem. In a gist - \, the tool you use should let you create special tools\nto learn smartly - from what you have already.\n\nSince we use Emacs\, let's make our great e - ditor moldable!\n\nThis talk shows my progress in making Emacs closer to s - uch a tool. We\nare going to see how we can mold structured (and maybe eve - n natural)\ntext to learn better\, how we can inject notes in our projects - and how\nself documenting this tool is!\n\nI aim to inspire you to find a - quicker way to learn from our digital\nworld!\n\nYou can learn more about - this at: <https://github.com/ag91/moldable-emacs>\n\n\n\n# Outline\n\n- - 5-10 minutes: quick demo of moldable-emacs + conf.org/2021/talks/mold\n END:VEVENT BEGIN:VEVENT SUMMARY:CLEDE the Common Lisp Emacs Development Environment. - Fermin MF @@ -1517,20 +654,10 @@ UID:daf3570b-3df3-9db4-a1f3-ce98d9863717 URL:https://emacsconf.org/2021/talks/clede DTSTART:20211128T195500Z DTEND:20211128T201500Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Fermin MF":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/clede\n# CLEDE the Common Lisp Emacs Development Envir - onment.\nFermin MF\n\n\n\nI've been developing a package that helps with t - he development of\nCommon Lisp's software\,\nit's uses the internal semant - ic framework\, it has a custom reader\nand integration for\ncommon Emacs p - ackages (like Sly and the internal inferior-lisp-mode).\n\nThe idea is to - supply features that other language with and static\nanalyzer have\,\nlike - refactoring and code generation.\n\nFor more details: <https://gitlab.com - /sasanidas/clede>\n\n- 20 minutes:\n It seems like not too much peopl - e knows about semantic\, so I can\n summarize some of it in 10 minutes\ - n and then An explanation on how to use the package\, how to extend it - \n and the future of it. + conf.org/2021/talks/clede\n END:VEVENT BEGIN:VEVENT SUMMARY:Imaginary Programming - Shane Mulligan @@ -1540,31 +667,10 @@ UID:f03ae971-4d2b-ccc4-2643-4ae2391ce1ab URL:https://emacsconf.org/2021/talks/imaginary DTSTART:20211128T202200Z DTEND:20211128T203300Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Shane Mulligan":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/imaginary\n# Imaginary Programming\nShane Mulligan\n\n - \n\nImaginary Programming (IP) is both methodology and paradigm. It is an\ - nextension of literate programming and a way of creating software without\ - nthe use of imperative\, functional or even declarative code. Yet IP emplo - ys\nall disciplines to achieve the miraculous. The only contingency is on - one\nor more language models\, known as foundation models. The real value - of IP\nis not found by abandoning sound logic altogether\, but in weaving - the real\nwith the imaginary. The future of imaginary programming is one i - n which\nalmost all of computing is inferred. I have built a suite of tool - s based on\nemacs for interfacing real programming languages with imaginar - y ones\; all\nof this in order to demonstrate what I mean\; a ‘complex’ te - rminal that lets\nyou imagine what happens no matter how nested you are wi - thin interpreters\,\nan example-oriented language\, a file format that enc - odes the provenance of\ntext and a library for imaginary functional progra - mming primitives called\niLambda. It is important to recognise IP because\ - , for lack of a better\nterm\, it has far-reaching implications for intell - ectual property and the\nGPL. Please keep an open mind.\n\n\n\n# Outline\n - \n- 5-10 minutes:\n- a 5 minute introduction to imaginary programming\ - , followed by\n - a demonstration of iLambda.\n - iλ\, a fam - ily of imaginary programming libraries\n <https://mullikine.github. - io/posts/designing-an-imaginary-programming-ip-library-for-emacs/>\n\n\n\n - IRC libertyprime at #emacs on libera\n\nShane Mulligan + conf.org/2021/talks/imaginary\n END:VEVENT BEGIN:VEVENT SUMMARY:How to build an Emacs - Fermin MF @@ -1574,21 +680,10 @@ UID:27595637-b6b9-f764-805b-ff1b7f009006 URL:https://emacsconf.org/2021/talks/build DTSTART:20211128T203600Z DTEND:20211128T205600Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Fermin MF":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/build\n# How to build an Emacs\nFermin MF\n\n\n\nThis - is a deep dive in the Emacs philosophical and technical\naspect on what ma - kes our beloved GNU Emacs\nwhat it it. It's also a talk about the early LI - SP machines and\nfascinating were those days of experimentation and engine - ering.\n\nIt will continue with the Emacs benefits/trade-offs from an\nuse - r/developer stand points\, what things can be improved and\nwhat can be an - hypothetical path on how to build a software that\ncan also be called Ema - cs.\n\nAs a last part\, I'll talk about CEDAR\, an Emacs that I've been\nd - eveloping in Common Lisp\, the project goals\nand the challenges.\n\nFor m - ore details about CEDAR: <https://gitlab.com/sasanidas/cedar>\n\n- 40 mi - nutes:\n A dive into the Emacs/Lisp machines history\, what makes GNU E - macs\n an Emacs and how you can build an Emacs. + conf.org/2021/talks/build\n END:VEVENT BEGIN:VEVENT SUMMARY:M-x Forever: Why Emacs will outlast text editor trends - David Wils @@ -1599,21 +694,10 @@ UID:80d1ad02-5fe4-03b4-c573-17ea6cdb61aa URL:https://emacsconf.org/2021/talks/forever DTSTART:20211128T210300Z DTEND:20211128T214300Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="David Wilson (System Crafters)":invalid:nomail DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/forever\n# M-x Forever: Why Emacs will outlast text ed - itor trends\nDavid Wilson\n\n\n\nThe computer software industry has seen m - any "popular" text editors come\nand go\, often due to the mercurial fashi - ons of software development. In\nthis talk\, we'll take a look at why pop - ular editors fade and the\nspecific aspects of Emacs that will ensure it r - emains relevant\nregardless of mainstream popularity.\n\n\n\n# Outline\n\n - - Discuss the core thesis\, the features that make Emacs\n desirable for - long-term use (extensibility\, day-to-day 'life' features)\n\n- Include mo - re background on the text editor landscape and\n how the scope of various - editors is more narrow and doesn't compare to Emacs.\n\n- Talk about spec - ific instances where editors were popular\, fell out\n of popularity\, an - d why (due to changing fashions\, not usually\n better features). + conf.org/2021/talks/forever\n END:VEVENT BEGIN:VEVENT SUMMARY:Closing remarks day 2 @@ -1623,8 +707,8 @@ UID:828e7c62-8430-f1a4-431b-63c308d58688 URL:https://emacsconf.org/2021/talks/day2-close DTSTART:20211128T215000Z DTEND:20211128T220000Z -DTSTAMP:20211113T170719Z +DTSTAMP:20211114T003833Z DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs - conf.org/2021/talks/day2-close\n# Closing remarks day 2 + conf.org/2021/talks/day2-close\n END:VEVENT END:VCALENDAR
\ No newline at end of file diff --git a/2021/info/model-schedule.md b/2021/info/model-schedule.md index 55a86db3..bde0e814 100644 --- a/2021/info/model-schedule.md +++ b/2021/info/model-schedule.md @@ -1,6 +1,6 @@ <!-- Automatically generated by conf-create-info-pages --> -Status: Prerecorded video received, waiting for captions +Status: Captions added to video Duration: 10 minutes Friendly URL: <a href="/2021/talks/model">/2021/talks/model</a> diff --git a/2021/schedule-details.md b/2021/schedule-details.md index 77a755ad..3371b1f4 100644 --- a/2021/schedule-details.md +++ b/2021/schedule-details.md @@ -1,5 +1,4 @@ -<table width="100%"><tr><th>Status</th><th>Start</th><th>Title</th><th>Speaker(s)</th></tr><tr><td colspan="4"><strong>Saturday, Nov 27, 2021: General talks<strong></td></tr> -<tr><td colspan="4"><strong>Saturday morning<strong></td></tr> +<table width="100%"><tr><th>Status</th><th>Start</th><th>Title</th><th>Speaker(s)</th></tr><tr><td colspan="4"><strong>Saturday morning<strong></td></tr> <tr><td></td><td width=100>~ 9:00 AM</td><td><a href="/2021/talks/day1-open">Opening remarks</a></td><td></td></tr> <tr><td>captioned</td><td width=100>~ 9:05 AM</td><td><a href="/2021/talks/news">Emacs News Highlights</a></td><td>Sacha Chua</td></tr> <tr><td>captioned</td><td width=100>~ 9:11 AM</td><td><a href="/2021/talks/frownies">The True Frownies are the Friends We Made Along the Way: An Anecdote of Emacs's Malleability</a></td><td>Case Duckworth</td></tr> @@ -42,7 +41,7 @@ <tr><td></td><td width=100>~10:06 AM</td><td><a href="/2021/talks/ui">"Yak-shaving to a UI framework" (/"Help! I accidentally yak-shaved my way to writing a UI framework because overlays were slow")</a></td><td>Erik Anderson</td></tr> <tr><td></td><td width=100>~10:19 AM</td><td><a href="/2021/talks/rust">Extending Emacs in Rust with Dynamic Modules</a></td><td>Tuấn-Anh Nguyễn</td></tr> <tr><td></td><td width=100>~10:44 AM</td><td><a href="/2021/talks/eaf">Emacs Application Framework: A 2021 Update</a></td><td>Matthew Zeng</td></tr> -<tr><td>received</td><td width=100>~10:58 AM</td><td><a href="/2021/talks/model">Extending the "model" of Emacs to other applications</a></td><td>Laszlo Krajnikovszkij</td></tr> +<tr><td>captioned</td><td width=100>~10:58 AM</td><td><a href="/2021/talks/model">Extending the "model" of Emacs to other applications</a></td><td>Laszlo Krajnikovszkij</td></tr> <tr><td></td><td width=100>~11:11 AM</td><td><a href="/2021/talks/devel">Don't write that package! or: How I learned to stop worrying and love emacs-devel</a></td><td>Stefan Kangas</td></tr> <tr><td>received</td><td width=100>~11:36 AM</td><td><a href="/2021/talks/bindat">Turbo Bindat</a></td><td>Stefan Monnier</td></tr> <tr><td colspan="4"><strong>Sunday afternoon<strong></td></tr> |