diff options
Diffstat (limited to '2021')
111 files changed, 1710 insertions, 1614 deletions
diff --git a/2021/emacsconf-pentabarf.xml b/2021/emacsconf-pentabarf.xml index e237d77f..45e959bc 100644 --- a/2021/emacsconf-pentabarf.xml +++ b/2021/emacsconf-pentabarf.xml @@ -1,10 +1,12 @@ -<schedule><generator name="EmacsConf" version="0.1"></generator><version>20211113094501</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>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. # 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. # Emacs News Highlights Sacha Chua <mailto:sacha@sachachua.com> - pronouns: she/her + + Quick overview of Emacs community highlights since the last conference You can find the links and images at @@ -22,6 +24,8 @@ Posting the video early to help test formatting. # The True Frownies are the Friends We Made Along the Way: An Anecdote of Emacs's Malleability Case Duckworth + + 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 @@ -53,6 +57,8 @@ teeth into. # Emacs as Design Pattern Learning Greta Goetz + + 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). 1. Definition of design patterns and relation to Emacs @@ -126,6 +132,8 @@ fair use.</description><url>https://emacsconf.org/2021/talks/pattern</url><perso # GNU's Not UNIX: Why Emacs Demonstrates The UNIX Philosophy Isn't Always The Only Answer Daniel Rose + + 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 @@ -152,6 +160,8 @@ to be more performant than without. # Emacs manuals translation and OmegaT Jean-Christophe Helary + + 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. 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. @@ -206,6 +216,8 @@ People who are interested in knowing more about OmegaT are invited to check the # 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 @@ -220,6 +232,8 @@ want their packages to be added to the repository.</description><url>https://ema # 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 @@ -241,6 +255,8 @@ Another Package and install all elisp code manually - with borg[1]. # 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 @@ -254,6 +270,8 @@ highlight some of the most important features.</description><url>https://emacsco # 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 @@ -283,6 +301,8 @@ If time, questions will be entertained by video/audio and/or IRC.</description>< # 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 @@ -300,6 +320,8 @@ Because of a reckless former Emacs maintainer that shall # 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. @@ -313,6 +335,8 @@ care of Emacs maintainance by taking care of Emacs maintainers. # 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 @@ -337,6 +361,8 @@ own scores. # 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 @@ -379,6 +405,8 @@ drives present in everybody that allow us to explore and make sense of our world # 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 @@ -401,6 +429,8 @@ research communities similar to ours.</description><url>https://emacsconf.org/20 # 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 @@ -418,6 +448,8 @@ inspire others to build workflows that make them more productive. # 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 @@ -474,6 +506,8 @@ estimate this at approx 10 minutes.</description><url>https://emacsconf.org/2021 # 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 @@ -500,6 +534,8 @@ org-treeslide to write and present technical documentation with style. # 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. @@ -551,6 +587,8 @@ adding a shebang block, and then running an org file.</description><url>https:// # 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. @@ -575,6 +613,8 @@ or they have adapted Org mode in their workflows already.</description><url>http # 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. @@ -614,6 +654,8 @@ I have create a git repository with examples and config files that is ready to u # 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 @@ -644,6 +686,8 @@ to Doom. # 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 @@ -692,6 +736,8 @@ examples to highlight some of the features mentioned in the abstract.</descripti # 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 @@ -745,6 +791,8 @@ from Org-mode documents. # 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. @@ -761,6 +809,8 @@ year, now, and with which we are very happy. Talk duration: # 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, @@ -791,6 +841,8 @@ We will use the following packages: # 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 @@ -864,6 +916,8 @@ easily managed from Emacs within a single Org-Mode file. # 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 @@ -891,6 +945,8 @@ You can learn more about this at: <https://github.com/ag91/emacs-with-nyxt> # 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 @@ -926,6 +982,8 @@ John Wiegley</description><url>https://emacsconf.org/2021/talks/dev-update</url> # 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 @@ -959,6 +1017,8 @@ by it and thus reserve the right to modify it ahead of the main event.</descript # How to write faster Emacs Lisp Dmitry Gutov + + - Before optimizing, benchmark first. - Different benchmarking approaches. - Live evaluation, step-debugging, measuring from a debugger breakpoint. @@ -972,6 +1032,8 @@ Dmitry Gutov # 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 @@ -1006,6 +1068,8 @@ Check out the GitHub repo [here](https://github.com/ethan-leba/tree-edit)! # 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 @@ -1040,6 +1104,8 @@ self-describing modal programming system. # "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 @@ -1063,6 +1129,8 @@ by implementing some basic UI's. # 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 @@ -1082,6 +1150,8 @@ dynamic modules in Rust. # 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 @@ -1096,6 +1166,8 @@ last year, this talk will briefly go over them. # 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 @@ -1155,6 +1227,8 @@ productivity, computer literacy and the ideas of free software. # 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 @@ -1184,6 +1258,8 @@ learn to love emacs-devel? Listen to my talk to find out more!</description><ur Stefan Monnier + + # Table of Contents @@ -1205,6 +1281,8 @@ show how we saved those. Not recommended for birds. # 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 @@ -1227,6 +1305,8 @@ Format: 40 minutes</description><url>https://emacsconf.org/2021/talks/native</ur # 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 @@ -1246,6 +1326,8 @@ modular, flexible Emacs Lisp. # 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. @@ -1281,6 +1363,8 @@ Eduardo Ochs <http://angg.twu.net/emacsconf2021.html></description><url>ht # 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 @@ -1291,6 +1375,8 @@ tracker? # 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. @@ -1387,6 +1473,8 @@ References: # 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. @@ -1421,6 +1509,8 @@ You can learn more about this at: <https://github.com/ag91/moldable-emacs> # 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 @@ -1442,6 +1532,8 @@ For more details: <https://gitlab.com/sasanidas/clede> # 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 @@ -1478,6 +1570,8 @@ Shane Mulligan</description><url>https://emacsconf.org/2021/talks/imaginary</url # 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 @@ -1501,6 +1595,8 @@ For more details about CEDAR: <https://gitlab.com/sasanidas/cedar> # 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 diff --git a/2021/emacsconf.ics b/2021/emacsconf.ics index 5d83a691..ea121645 100644 --- a/2021/emacsconf.ics +++ b/2021/emacsconf.ics @@ -13,7 +13,7 @@ UID:dc07efcd-6d79-cfd4-fed3-59c885fe2922 URL:https://emacsconf.org/2021/talks/day1-open DTSTART:20211127T140000Z DTEND:20211127T140500Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs conf.org/2021/talks/day1-open\n# Opening remarks END:VEVENT @@ -25,16 +25,16 @@ UID:393ba3c2-b2a6-6a84-44eb-872aa333d08d URL:https://emacsconf.org/2021/talks/news DTSTART:20211127T140500Z DTEND:20211127T141000Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nQuick overview of Emacs community - highlights since the last conference\n\nYou can find the links and images - at\n<https://github.com/sachac/emacsconf-2021-emacs-news-highlights>\n\nPo - sting the video early to help test formatting.\n\n\n\n# Questions\, answer - s\, and community-provided links\n\n<a name="transcript"></a>\n# Transcrip - t + 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 END:VEVENT BEGIN:VEVENT SUMMARY:The True Frownies are the Friends We Made Along the Way: An Anecdot @@ -45,29 +45,29 @@ UID:06df8309-bd04-eb24-d443-a780c56adc0a URL:https://emacsconf.org/2021/talks/frownies DTSTART:20211127T141100Z DTEND:20211127T143100Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nEmac - s is well-known for being extremely flexible\, programmable\, and\nextensi - ble\; in fact\, that's probably the biggest reason it's still\nbeing used - after 40+ years of existence\, and even has enough clout to\ngenerate an e - ntire conference in its name. In this medium-length\npresentation\, I wil - l add another point to the data set proving Emacs's\nabilities\, by narrat - ing the latest package I made\, \\`frowny.el\\`\, from\nits conception to - its current\, nearly-completed state.\n\nI wrote frowny.el to scratch some - one else's itch as a joke on IRC\, but\nit has been called "pretty useful\ - , for a joke package." I feel like\nthat encapsulates the spirit of Emacs - 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## Speake - r information\n\n- Name pronunciation: /keɪs ˈdʌkwə(ɹ)θ/ (CASE DUCK-worth) - \n- Prounouns: he/him\n- Homepage: <https://www.acdw.net>\n- Preferred con - tact info: [email](mailto:acdw@acdw.net)\n- Links:\n - <https://breadpunk - .club>\, a shared unix server about bread\n - [my Mastodon account](https - ://writing.exchange/@acdw) (though I'm moving to\n[tiny.tilde.website](htt - ps://tiny.tilde.website/@acdw) ... soon™) + 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™) END:VEVENT BEGIN:VEVENT SUMMARY:Emacs as Design Pattern Learning - Greta Goetz @@ -77,90 +77,90 @@ UID:fe959e43-441b-ed34-854b-87f6f481f55a URL:https://emacsconf.org/2021/talks/pattern DTSTART:20211127T143400Z DTEND:20211127T145800Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nHow do we manage today? This presentation is for people interested i - n thinking about Emacs as a tool sophisticated enough to cater to the comp - lex assemblage of tasks\, people\, activities/outcomes\, tools (Markauskai - te & Goodyear). Some software oversimplifies. Emacs both helps users imple - ment design pattern learning that can cope with complexity while also mode - ling design pattern learning. By championing the opportunity for users to - also be co-creators (cf. Beaty et al.)\, the free software design at the c - ore 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 knowled - ge of how to live (Stiegler\, Illich).\n\n1. Definition of design pattern - s and relation to Emacs\n2. Why this approach matters\n3. Managing compl - exity: Emacs as mind map\n4. Emacs as design pattern framework\n5. Perso - nal customization\n6. Implementing Emacs as a model for learning\n7. Ema - cs as accommodating complex social\, community assemblages\n\n# References - \n\n- Andler\, D. & Guerry\, B. (Eds.). *Apprendre demain: Sciences cogn - itives et éducation à l’ère numérique*\, 137-154. Paris: Hatier.\n- Alex - ander\, C. (1977). *A pattern language*. New York: Oxford University Press - .\n- Alexander\, C. (1979). *The timeless way of building*. New York: Ox - ford University Press.\n- Alexander\, C. (1993). *A foreshadowing of 21s - t century art: The color and geometry of very early Turkish carpets*. New - York: Oxford University Press.\n- 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://w - ww.lancs.ac.uk/fss/organisations/netlc/past/nlc2010/abstracts/PDFs/Beaty.p - df. Accessed 30 October 2021.\n- Chua\, S. (2021). Completing sketches. - https://sachachua.com/dotemacs/#org092e0d5. Accessed 29 October 2021.\n- - Crichton\, M. (1983). *Electronic life*. New York: Knopf.\n- Gabriel\, - R. (1996). *Patterns of software*. New York\, Oxford: Oxford University Pr - ess.\n- Goodyear\, P. & Retalis\, S. (2010). Learning\, technology and d - esign. In Goodyear\, P. & Retalis\, S. (Eds.). *Technology-enhanced learni - ng: Design patterns and pattern languages*\, 1-27. Rotterdam\, Boston: Sen - se Publishers.\n- Guo\, P. (2018). Students\, systems\, and interactions - : Synthesizing the first\nfour years of Learning@Scale and charting the fu - ture. 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.\n- 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>. Acces - sed 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 int - eraction peaks in online lecture videos. ACM Conference on Learning at Sca - le. <https://pg.ucsd.edu/pubs.htm>. Accessed 25 October 2021.\n- Markaus - kaite\, L. & Goodyear\, P. (2017). *Epistemic fluency and professional edu - cation: innovation\, knowledgeable action and actionable knowledge*. Dordr - echt: Springer.\n- Markel\, J. & Guo\, P. (2020). Designing the future o - f 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.\n- Morin\, E. ([2004] 2008). *La Méthode - tome 6: Éthique*. Éditi - ons du Seuil: Paris.\n- Planet Emacs Life. <https://planet.emacslife.com - />. Accessed 25 October 2021\n- Stallman\, R. (2002). My Lisp experience - s and the development of GNU Emacs. https://www.gnu.org/gnu/rms-lisp.en.ht - ml. Accessed 29 October 2021.\n- Stiegler\, B. (2018). *The neganthropoc - ene*. Open Humanities Press.\n- Trocmé-Fabre\, H. (1999). *Réinventer le - métier d’apprendre*. Paris: Éditions d’organisation.\n\n\n# Availability - and preferred Q&A approach\n\nDue to the pandemic situation\, my teaching - schedule fluctuates so I\nwill not know my availability until much closer - to the\ndate. Therefore\, I can only guarantee delayed answer response\n(w - hatever you request)\, but if available\, will join live.\nMay I please no - te that I will be pre-recording my video if this submission is accepted.\n - \n\n# Speaker release\n\nBy submitting this proposal\, I agree that my pre - sentation at\nEmacsConf 2021 is subject to the following terms and conditi - ons:\n\nThe EmacsConf organizers may capture audio and video (a "Recording - ")\nof my presentation and any associated materials\, which may include\ns - lides\, notes\, transcripts\, and prerecording(s) of my presentation\nthat - I provide to the EmacsConf organizers.\n\nI authorize the EmacsConf organ - izers to distribute\, reproduce\,\npublicly display\, and prepare derivati - ve works of the Recording and\nany derivative works of the Recording (the - "Licensed Materials")\nunder the terms of the Creative Commons Attribution - -ShareAlike 4.0\nInternational (CC BY-SA 4.0) license.\n\nI grant to the E - macsConf organizers permission to use my name\,\nlikeness\, and biographic - information in association with their use\nof the Licensed Materials unde - r the above license.\n\nI represent that I have the authority to grant the - above license to\nthe EmacsConf organizers. If my presentation incorporat - es any\nmaterial owned by third parties\, I represent that the material is - \nsublicensable to the EmacsConf organizers or that my use of them is\nfai - r use. + 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. END:VEVENT BEGIN:VEVENT SUMMARY:GNU's Not UNIX: Why Emacs Demonstrates The UNIX Philosophy Isn't Al @@ -171,26 +171,26 @@ UID:ea5bab3c-f31e-68a4-fa23-81ca67fa1990 URL:https://emacsconf.org/2021/talks/unix DTSTART:20211127T150000Z DTEND:20211127T150700Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nThe talk targets - users who are curious about computational philosophies\,\nor those who mi - ght not know how to best utilise Emacs conceptually. The\ntalk will cover - what the UNIX philosophy is\, the GNU Free Software\nprinciples\, a typica - l (Neo)Vi(m) user's approach\, and then how one might\naccomplish this in - Emacs combining the aformentioned ideals. The\nlisteners will learn how th - ey can approach Emacs ideologically\, and how\nblocking themselves into on - e philosophy or the other will limit their\nefficiency. Although you may b - e a veteran GNU/Linux and Emacs user\,\nunderstanding how to use both phil - osophies together will still allow you\nto be more performant than without - .\n\n\n\n# Outline\n\n- How can one limit their usage of CLI tools while - still maintaining\n the ideals of both.\n- How using CLI tools c - an still perfectly flow into Emacs.\n- How having all programs in Emacs - and unified keybindings is akin\n to a terminal user.\n- Why thin - king about computational philosophies might itself be an\n impedime - nt. + 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. END:VEVENT BEGIN:VEVENT SUMMARY:Emacs manuals translation and OmegaT - Jean-Christophe Helary @@ -200,57 +200,57 @@ UID:db4ccb28-867f-df24-c073-eaca6edad438 URL:https://emacsconf.org/2021/talks/omegat DTSTART:20211127T151100Z DTEND:20211127T152100Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nEven if it is generally agreed that software localizat - ion is a good thing\, Emacs is lacking in that respect for a number of tec - hnical reasons. Nonetheless\, the free software using public could greatly - benefit from Emacs manuals translations\, even if the interface were to r - emain in English.\n\nOmegaT is a multiplatform GPL3+ "computer aided trans - lation" (CAT) tool running on OpenJDK 8. CATs are roughly equivalent for t - ranslators to what IDEs are for code writers. Casual translators can benef - it from their features but professionals or committed amateurs are the mos - t likely to make the most use of such tools.\n\nWhen OmegaT\, free softwar - e based forges and Emacs meet\, we have a free multi-user translation envi - ronment that can easily sustain the (close to) 2 million words load that c - omprise 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.\n\nThe current trial project for - French is hosted on 2 different forges:\n\n1. sr.ht hosts the source file - s\n <https://sr.ht/~brandelune/documentation_emacs/>\n2. chapril hosts - the OmegaT team project architecture\n <https://forge.chapril.org/brand - elune/documentation_emacs>\n\nThe sources are regularly updated with a po4 - a based shell script.\n\n# Outline\n\n- Duration: 10 minutes\n- Software u - sed during the presentation\n - [po4a](https://po4a.org) a tool to conver - t documentation formats to and from the commonly used `gettext` **PO** for - mat.\n po4a supports the `texinfo` format along with many others.\n - - [OmegaT](https://omegat.org) a "computer aided translation" tool used by t - ranslators to efficiently combine translation resources (legacy translatio - ns\, glossaries\, etc.) so as to produce more consistent translations.\n\n - During this short presentation\, I will address:\n\n- The specificities 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-base - d system\n- How to convert the texi and org files to a format that transla - tors can handle\n- How to adapt OmegaT to the Emacs manual specificities\n - - How to use OmegaT features such as arbitrary string protection\, legacy - translation handling\, glossaries\, autocompletion\, QA\, etc.\n- How to u - se OmegaT with a team of 2 (or more) translators working at the same time\ - 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 w - ork in localization pipelines\n- How to use machine translation and MT "po - st-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 inter - ested in knowing more about OmegaT are invited to check the [online user m - anual](https://omegat.sourceforge.io/manual-latest/en/).\n\n# Personal inf - ormation\n- Name pronunciation: [ʒɑ̃kRstɔf elaRi](https://doublet.jp/wp-co - ntent/uploads/2021/11/jch.ogg)\n- Pronouns: he\n- Homepage: [https://mac4t - ranslators.blogspot.com](https://mac4translators.blogspot.com)\n- Preferre - d contact info: [jean.christophe.helary@traduction-libre.org](jean.christo - phe.helary@traduction-libre.org)\n- Links for sponsoring/supporting (multi - lingual translations): [https://doublet.jp](https://doublet.jp) + 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) END:VEVENT BEGIN:VEVENT SUMMARY:NonGNU ELPA Update - Philip Kaludercic @@ -260,17 +260,17 @@ UID:525d972d-1e34-bcb4-e9c3-861942549357 URL:https://emacsconf.org/2021/talks/nongnu DTSTART:20211127T152400Z DTEND:20211127T153100Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nNon - GNU ELPA was announced last year\, as a package repository\nthat will be e - nabled by default in Emacs\, but doesn't require\nany copyright assignment - . This means that a lot of popular\npackages can now be installed easier\, - without any additional\nconfiguration.\n\nIn this talk I would like the g - ive a reminder of what NonGNU\nELPA is and how it works\, update the parti - cipants on what has\nhappened since last year and what maintainers have to - do if they\nwant their packages to be added to the repository. + 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. END:VEVENT BEGIN:VEVENT SUMMARY:Manual Package Management in The Era of Repositories - Why and How @@ -281,19 +281,19 @@ UID:245a575a-965a-caa4-8d3b-75f8519c2f3e URL:https://emacsconf.org/2021/talks/borg DTSTART:20211127T153600Z DTEND:20211127T154400Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nEmacs now has many package r - epositories - enought to have conflicts\nand arguments about. The packages - 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 aggressi - ve way out of this is to use Yet\nAnother Package and install all elisp co - de manually - with borg[1].\n\n[1]: <https://github.com/emacscollective/bo - rg>\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 u - se it?\n 4. Assimilate a package for demo + 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 END:VEVENT BEGIN:VEVENT SUMMARY:telega.el and the Emacs community on Telegram - Gabriele Bozzola @@ -303,20 +303,20 @@ UID:86158391-53a2-7cb4-d7d3-020afbf6d8d9 URL:https://emacsconf.org/2021/talks/telega DTSTART:20211127T154800Z DTEND:20211127T155600Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nTelegram is a cross-platform inst - ant messaging system. The large number of\nfeatures and the widespread ado - ption make it a good choice for both private\nconversations with friends a - nd 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 disc - uss telega.el\, the Emacs client for Telegram. telega.el\nis a high-qualit - y package that perfectly integrates in Emacs. It supports\nthe vast majori - ty of the features supported by the official clients\, while\nadding sever - al unique ones. In the talk\, I will present the package and\nhighlight so - me of the most important features. + 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. END:VEVENT BEGIN:VEVENT SUMMARY:Introducing N-Angulator - Kevin Haddock @@ -326,22 +326,22 @@ UID:e4bdc2c1-e4b6-67e4-aafb-87ec9aaf846b URL:https://emacsconf.org/2021/talks/nangulator DTSTART:20211127T155800Z DTEND:20211127T160800Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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 - \nThe Unix file system is essentially an N-dimentional sparse array that\n - currently lacks a decent editor and browser which\ncan effectively leverag - e the logical tri-angulation (or\, more properly\n"n-angulation") of atoms - /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 uncircu - lated prototype\nvideo demo. Be sure and turn the volume UP!)\n\nna.intr - o.flv\n<https://drive.google.com/file/d/1EZN0Xs8eGlEbSIYFml2lp3GCNnmLQa98/ - view?usp=drive_web>\n\n\n\n# Outline\n\n- 5-10 minutes: (brief descripti - on/outline)\n\nThe reconceptualization of the Unix file system as the N-Di - mensional\nsparse array will be discussed.\n\nA simple pre-existing databa - se will be queried.\n\nIf time\, questions will be entertained by video/au - dio and/or IRC. + \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. END:VEVENT BEGIN:VEVENT SUMMARY:A day in the life of a janitor - Stefan Monnier @@ -351,21 +351,21 @@ UID:14ab7a54-d75d-45e4-85ab-8fd2e391ea41 URL:https://emacsconf.org/2021/talks/janitor DTSTART:20211127T161100Z DTEND:20211127T163700Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nBecause of a reckless former Emacs maintainer that shall\n better - stay unnamed\, ELisp has seen a fair bit of churn in the last 10\n years\ - , making it necessary to clean up "old" code [in order to open up\n the r - oad for yet more recklessness? ].\n In this documentary we will follow a - famous janitor in his every day job\n dealing with the aftermath of the c - l-lib / lexical-binding party.\n\n- ~20 minutes\n Here really\, I'm n - ot sure how much time this will take. I put 20\n minutes because I thi - nk 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\, wit - hout anything like an outline: it's basically "make"\n followed by fixi - ng the warnings. + 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. END:VEVENT BEGIN:VEVENT SUMMARY:How to help Emacs maintainers? - Bastien Guerry @@ -375,14 +375,14 @@ UID:51c360e6-188f-9a34-05bb-0a8d2eb09cdc URL:https://emacsconf.org/2021/talks/maintainers DTSTART:20211127T164200Z DTEND:20211127T165200Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nAfter 11 years of helping as the Org maintainer\, I would\nlike - to share a few lessons learned. My goal is help everyone take\ncare of E - macs maintainance by taking care of Emacs maintainers.\n\n\n\n# Outline\n\ - n- 5-10 minutes + 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 END:VEVENT BEGIN:VEVENT SUMMARY:Typesetting Gregorian Chant with Emacs - Spencer King @@ -392,22 +392,22 @@ UID:716d913f-de8b-91a4-5f33-e04ba0905fa5 URL:https://emacsconf.org/2021/talks/gregorian DTSTART:20211127T165500Z DTEND:20211127T170500Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nThere are a variety of methods for typesetting gregorian\nc - hant scores and outputting high-quality sheet music. One of these is\na to - ol called Gregorio\, which integrates with LaTeX allowing scores to\nbe cl - eanly inserted into other documents. All Gregorio files are plain\ntext\, - allowing them to easily be shared with other users and managed\nwith a ver - sion control system. In this talk\, I will give a brief\noverview of the G - regorio tool and then show how it can be used in\nEmacs by typesetting a s - imple score. All code and examples will be\nmade available to help new use - rs get started with typesetting their\nown scores.\n\n\n\n# Outline\n\n- - 5-10 minutes: (brief description/outline)\n 1. Introduction to chant - music\n 2. Introduction to Gregorio\n 3. Example of typesetting a - score in Emacs\n 4. Code and example availability + 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 END:VEVENT BEGIN:VEVENT SUMMARY:Emacs and Montessori Philosophy - Grant Shangreaux @@ -417,31 +417,31 @@ UID:6fccae45-04b5-5524-662b-fdba87754d06 URL:https://emacsconf.org/2021/talks/montessori DTSTART:20211127T173000Z DTEND:20211127T174000Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nAs - a former Montessori guide and now parent\, I often think about the\nrelati - onship of this particular educational philosophy and how it manifests\nin - my work with software\, Emacs in particular. This talk introduces the\ncon - cept of Emacs as an educational environment and how it expresses elements - of\nMontessori psychology regarding "Human Tendencies". Human tendencies a - re innate\ndrives present in everybody that allow us to explore and make s - ense of our world.\n\n\n\n# Outline\n\n- 5-10 minutes: (brief descriptio - n/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 limits - )\n - the environment itself is prepared specifically to foster engag - ement\n\n Enumerate the "Human Tendencies":\n\n - Abstraction\n - - Activity\n - Communication\n - Exactness\n - Explorati - on\n - Manipulation (of the environment)\n - Order\n - Orie - ntation\n - Repetition\n - Self-Perfection\n - Work (also d - escribed as "purposeful activity")\n\n How does Emacs express these thi - ngs?\n\n - in the short version\, pose the question\, and perhaps giv - e one example.\n - Emacs is an environment that provides facilities f - or individuals to\n find their way to proficiency through their Hum - an Tendencies.\n - We are all both learners and guides\, Emacs is our - classroom + 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 END:VEVENT BEGIN:VEVENT SUMMARY:Emacs Research Group\, Season Zero: What we did together with Emacs @@ -453,7 +453,7 @@ UID:9cee7e43-bcb1-7f64-c40b-5f9ea938d11a URL:https://emacsconf.org/2021/talks/erg DTSTART:20211127T174300Z DTEND:20211127T175800Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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 @@ -461,23 +461,23 @@ 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\nThe four of us met at EmacsConf 2020 - \, and joined together around a\ncommon interest in Emacs and research. S - ince then\, we have convened as\nthe Emacs Research Group for weekly meeti - ngs. During these meetings\, we\ntook notes collaboratively\, using a ‘co - nflict-free replicated data type’\npackage (crdt.el)\; at the end of each - session\, we debriefed using a\ntemplate that we call a Project Action Rev - iew (PAR). As as a\nmeta-review of our sessions\, every six weeks we prep - ared a Causal\nLayered Analysis (CLA)\, which gave us a different perspect - ive on what we\nhad done. We reflected further on our experiences and met - hods\, linking\nour CLA to plans and design patterns. As a formal researc - h output\, we\ncontributed a write-up of these matters to a joint paper wh - ich we\npresented at the Pattern Languages of Programs Conference (PLoP 20 - 21).\nThe paper included an interactive workshop\, in which we explored ro - les\nin real-time problem solving and collaboration.\n\nIn our short talk - we share information about these methods\, making a\ncase for other people - getting together and creating their own small\nresearch communities simil - ar to ours. + 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. END:VEVENT BEGIN:VEVENT SUMMARY:One effective CS grad student workflow - Greg Coladonato @@ -487,19 +487,19 @@ UID:0f98a5bb-53ce-fb74-1003-0b1f320d414e URL:https://emacsconf.org/2021/talks/cs DTSTART:20211127T180100Z DTEND:20211127T181100Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nWhen I was an undergrad\, I learned many things\, most of\nwhic - h I forgot. In the time since then\, I've discovered Org Mode\, Org\nRoam\ - , Org Noter\, Org Ref. PDF Tools\, and Anki. I would like to share\nmy app - roach for capturing all the information that comes my way as a\nMS CS stud - ent at Georgia Tech\, in the hopes that I can both get\nfeedback on ways t - o improve the system I use\, as well as hopefully\ninspire others to build - workflows that make them more productive.\n\n\n\n# Outline\n\n- 5-10 mi - nutes: Go through some typical workflows associated with being a grad stud - ent\, using the packages mentioned in the abstract. + 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. END:VEVENT BEGIN:VEVENT SUMMARY:Using Org-Mode For Recording Continuous Professional Development - @@ -510,41 +510,41 @@ UID:43cc5db4-e26f-fb44-9aeb-b16c38d8cef3 URL:https://emacsconf.org/2021/talks/professional DTSTART:20211127T181400Z DTEND:20211127T182500Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nI recently had the pleasure - of being audited for my CPD record with one\nof the large engineering pro - fessional bodies. I decided to harness\norg-mode's TODO lists to record C - PD items and my progress against them\ncompletely within Emacs. I also wa - nted the ability to export the data\nin a well presented\, compact format - for auditing submission.\n\nThe project was a success (I passed the audit) - and the resulting system\nintegrates really well into my wider daily Emac - s workflow\, making future\nCPD recording seamless.\n\nThe talk will expla - in how I tweaked and extended org-mode to get it to\nrecord the data I wan - ted\, followed by a demo.\n\nA basic demo org file with embedded elisp can - be seen here:\n<https://raw.githubusercontent.com/falloutphil/Misc/master - /cpd.org>\n\nA basic generated PDF from the basic demo is here:\n\n\nI have a much more involved e - xample I could also use for the demo.\n\nThe template contains a few examp - les. Examples are Goals that are split\nup into Activities. All Activitie - s must have a Goal\, and within a Goal\nall activities must be complete fo - r the Goal to be automatically set to\ncomplete.\n\nIt's basically leverag - ing Org Capture Templates to create custom Goals\nand Activities.\n\nOn sa - ve or update these are then rendered into a table using Column View.\n\nAc - tivities 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 format f - or submission. It stays fairly readable even when\nthe pages get busy.\n\n - The 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\nnice - custom org capture functions and a few functions to ensure nice\nformattin - g on export\, etc.\n\n\n\n# Outline\n\n- 5-10 minutes:\n\nA quick walkth - rough of the setup and functions\, followed by a demo of how\nto add CPD i - tems\, and update them. Finally show generation of a PDF\ncontaining all - the items tabulated and ready for audit review. I\nestimate this at appro - x 10 minutes. + 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. END:VEVENT BEGIN:VEVENT SUMMARY:Creating technical API documentation and presentations using org-ba @@ -555,23 +555,23 @@ UID:a10ce62e-6454-d784-21bb-f6a0488e883c URL:https://emacsconf.org/2021/talks/tech DTSTART:20211127T182700Z DTEND:20211127T183800Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nThe - emacs org-babel package is often mentioned in conjunction with\nliterate - programming. The ability to mix code segments with prose\nindeed offers an - intuitive way to augment semantic code pieces with\ntextual descriptions. - \n\nIn recent projects\, I've started to turn to org-mode as the primary\n - format to maintain technical documentation\, as well as slides for a\ntech - nical language course. By using org-babel to pull in "live" code\nfor REST - requests\, language examples\, and shell scripts\, one can be\nsure that - the documentation and slides are never out of date.\n\nThe session will sh - ow how leverage org-babel\, restclient and\norg-treeslide to write and pre - sent technical documentation with style.\n\n\n# Outline\n\n- Introduction\ - n- Demo: Developer guide\n- Demo: REST API guide\n- Demo: Presentations\n- - Used packages and configuration + 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 END:VEVENT BEGIN:VEVENT SUMMARY:Org as an executable format - Tom Gillespie @@ -581,36 +581,36 @@ UID:b092bc88-e74c-a9c4-611b-d47c99ef578c URL:https://emacsconf.org/2021/talks/exec DTSTART:20211127T184000Z DTEND:20211127T184800Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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 - Org mode is known for its flexibility\, power\, and staggeringly diverse\n - number of workflows\, users\, and use cases.\n\nThis talk explores just ho - w 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 elvs: - two parts of a\ncomplete system for creating executable Org files.\n\nOrg - syntax does not support shebang lines. However\, it turns out that\nOrg s - yntax enables something even better —\; shebang blocks.\n\nOrg is al - so (supposedly) not an executable file format. However\, by\ncombining a - shebang block with a Org babel source block\, and eval\nlocal variables (e - lvs) Org becomes a multi-language executable format.\n\nIn this talk we in - troduce shebang blocks and elvs as a two part system\nthat transforms Org - files into executable documents that can run on any\nrecent version of Ema - cs.\n\nThese ideas are implemented in\n<https://github.com/tgbugs/orgstrap - /blob/master/README.org> and\n<https://github.com/tgbugs/orgstrap/blob/mas - ter/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 orgstrap m - achinery.\n\nWe then discuss security considerations\, and show example us - e 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\nsys - tems and shells\, and on the development of a formal specification\nand a - reference implementation for using Org source blocks to\ntransform Org fil - es from plain text documents with a bit of markup\ninto self describing co - mputational documents\, or interactive\napplications.\n\n\n\n# Outline\n\n - - 5-10 minutes:\n\nA demo of adding the orgstrap block and elvs\,\naddin - g a shebang block\, and then running an org file. + \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. END:VEVENT BEGIN:VEVENT SUMMARY:The use of Org mode syntax outside of GNU/Emacs - Karl Voit @@ -620,23 +620,23 @@ UID:69763d57-be4e-7e74-509b-92e48a0e7ba6 URL:https://emacsconf.org/2021/talks/org-outside DTSTART:20211127T185100Z DTEND:20211127T190300Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nWith the rising interest in Org mode\, the GNU/Emac - s community gained\nmuch momentum in the last decade. Being a nicely desig - ned lightweight\nmarkup language\, Org mode does not only benefit users of - GNU/Emacs.\nThere are many tools and services supporting Org mode syntax - documents\nthat do have no direct connection to GNU/Emacs. I would like to - \nelaborate on the advantages on using Org mode syntax for arbitrary\ntext - outside of GNU/Emacs for better typing usability and\ncollaboration tasks - .\n\n\n\n# Outline\n\n- 5-10 minutes: (brief description/outline)\n\nThi - s can only be a short teaser for the use of Org mode syntax without\nmuch - comparison to other lightweight markup languages. For this\naudience\, I d - o think that this would be too short because most\nattendees might already - have heard the rumors that Org mode is great\nor they have adapted Org mo - de in their workflows already. + 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. END:VEVENT BEGIN:VEVENT SUMMARY:Using Org-mode to teach programming - Daniel German @@ -646,28 +646,28 @@ UID:aed5e190-66a0-3dd4-e5eb-be09be94e6c3 URL:https://emacsconf.org/2021/talks/teach DTSTART:20211127T190400Z DTEND:20211127T192500Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nIn this presentation I will explain how to use org-mode effective - ly to\nprepare teaching materials\, and how to present them.\n\nFor the la - st 5 years I have been using org-mode to teach programming\nin different l - anguages: C++\, SQL\, Ruby\, Python\, SML\nand Scheme. Org-mode has three - key advantages:\n\n1. it supports most programming languages with a commo - n interface\,\n2. it is an interactive medium for delivering teaching mat - erials\; 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 m - y 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 for bo - th\nteaching and studying (see\n<https://github.com/dmgerman/csc116ModernC - plusplus/blob/master/lectures/l-01-1-intro/01_1_intro.org>\nfor an example - ).\n\nFinally\, I will discuss some important aspects to consider when usi - ng\norg-mode for this purpose.\n\n\n\n# Outline\n\n20 minutes:\n\n- Intr - oduction\n- Quick demonstration\n- Workflow\n- Some Important consid - erations\n- Emacs configuration and how to get started\n\nI have create - a git repository with examples and config files that is ready to use:\n<ht - tps://github.com/dmgerman/teachingProgOrg> + 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> END:VEVENT BEGIN:VEVENT SUMMARY:Managing a research workflow (bibliographies\, note-taking\, and ar @@ -678,26 +678,26 @@ UID:fd246cee-b5d6-7cc4-2b63-20e87bb7d750 URL:https://emacsconf.org/2021/talks/research DTSTART:20211127T192900Z DTEND:20211127T193400Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nResearchers and knowledge w - orkers have to read and discover new papers\,\nask questions about what th - ey read\, write notes and scratchwork\, and store\nmuch of this informatio - n for use in writing papers and/or code. Emacs allows\nus to do all of thi - s (and more) using simple text interfaces that integrate\nwell together. I - n this talk I will talk about the following:\n\na. Using elfeed and elfeed - -score to read new papers from arXiv.\nb. Using org-ref to import arXiv pa - pers of interest into a local\nbibliography.\nc. Using Emacs hooks with bi - ber and rebiber in order to keep the local\n bibliography clean and up-t - o-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\nT - his text-based workflow allows for keeping everything accessible under\nve - rsion\ncontrol and avoids the platform lock-in of binary formats (e.g. Men - deley). 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 will - demo the packages I use in 5 minutes. + 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. END:VEVENT BEGIN:VEVENT SUMMARY:Babel for academics - Asilata Bapat @@ -707,42 +707,42 @@ UID:db5821ed-fef4-4934-8fb3-87a0282714de URL:https://emacsconf.org/2021/talks/babel DTSTART:20211127T193800Z DTEND:20211127T194800Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nPlain o - rg-mode is already an extremely powerful and\ncustomisable tool for task a - nd time management\, note-taking\, calendar\nand agenda management\, and m - uch more. Babel takes org a step further\nby letting you write\, evaluate\ - , and export code in different languages\nfrom within a single file. In th - is talk\, I will highlight some\nfeatures of babel that I find exciting an - d extremely useful\,\nparticularly for an academic workflow.\n\nGetting st - arted with babel can be intimidating\, but it's hard to stop\nusing it onc - e you start. As an academic\, I typically don't manage\nlarge coding proje - cts. My primary purpose is writing lecture notes\,\nassignments\, and pape - rs\, and managing related admin. Typically\, I want\nto try and automate t - he boring portions of my workflow without extra\noverhead. I also tend to - find various tasks easier in some programming\nlanguages and harder in oth - ers\, and prefer to mix and match languages\nas the task dictates. Babel m - akes this process seamless.\n\nA basic use case is writing a document in o - rg-mode and exporting it to\nLaTeX or HTML. Org-mode even lets you write m - ultiple documents in a\nsingle org file\, which can be convenient. Babel l - ets you add all sorts\nof enhancements to the same file. For example\, sup - pose we have a\nsingle org document with all the problem sets for a course - . Within\nthis single file\, we could now:\n\n- draw pictures in ditaa\, - graphviz\, or python instead of LaTeX\,\n- use python to do complex cal - culations and then output the result as LaTeX\,\n- define skeletons to q - uickly draw up assignment templates\,\n- toggle exporting of assignments - with or without solutions based on tags\,\n- locally change export sett - ings or run a post-export hook\,\n- automatically export to LaTeX after - saving\,\n- tangle code blocks from some or all of the languages to exte - rnal files.\n\nI will try to showcase features of babel that academics cou - ld find\nhelpful\, by presenting some ways in which I have tried to use ba - bel. I\nwould also like to be inspired by other people's babel workflows!\ - n\n\n\n# Outline\n\n- 5-10 minutes: (brief description/outline)\n\nFor 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 highl - ight some of the features mentioned in the abstract. + 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. END:VEVENT BEGIN:VEVENT SUMMARY:Reproducible molecular graphics with Org-mode - Blaine Mooers @@ -752,44 +752,44 @@ UID:1fc4917c-aab4-1924-2983-e78f8bca6af9 URL:https://emacsconf.org/2021/talks/molecular DTSTART:20211127T195000Z DTEND:20211127T200100Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nResearch papers in structural biology should includ - e the code used to make\nthe images of molecules in the article in the sup - plemental materials.\nSome structural bioinformaticists have started to in - clude\ntheir computer code in the supplemental materials to allow readers\ - nto reproduce their analyses. However\, authors of papers reporting new\nm - olecular structures often overlook the inclusion of the code that makes\nt - he images of the molecules reported in their articles. Nonetheless\,\nthis - aspect of reproducible research needs to become the standard practice\nto - improve the rigor of the science.\n\nIn a literate programming document\, - the author interleaves blocks\nof explanatory prose between code blocks t - hat make the images of molecules.\nThe document allows the reader to repro - duce the images in the manuscript by running the code.\nThe reader can als - o explore the effect of altering the parameters in the\ncode. Org files ar - e one alternative for making such literate programming\ndocuments.\n\nWe d - eveloped a **yasnippet** snippet library called **orgpymolpysnips** for\ns - tructural biologists (<https://github.com/MooersLab/orgpymolpysnips>).\nTh - is library facilitates the assembly of literate programming documents\nwit - h molecular images made by PyMOL. PyMOL is the most popular\nmolecular gra - phics 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 covers o - f many Cell\, Nature\, and Science issues.\n\nWe used the **jupyter** lang - uage in **org-babel** to send commands from\ncode blocks in Org files to P - yMOL's Python API. PyMOL returns the\nmolecular image to the output block - below the code block. An Emacs\nuser can convert the Org file into a PDF\, - `tangle' the code blocks\ninto a script file\, and submit these for non-E - macs users. We describe\nthe content of the library and provide examples o - f the running PyMOL\nfrom Org-mode documents.\n\n\n# Outline\n\n- 5-10 m - inutes: (brief description/outline)\n - Title slide\n - Structur - al Biolog Workflow in the Mooers Lab\n - Cover images made with PyMOL - \n\n - Why develop a snippet library for your field?\n - PyMOL i - n Org: kernel specification\n - Creating a conda env and installing P - yMOL\n - Example code block in Org to make DSSR block model of tRNA\n - - Resulting image\n - Summary\n - Acknowledgements + 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 END:VEVENT BEGIN:VEVENT SUMMARY:Budgeting\, Project Monitoring and Invoicing with Org Mode - Adolfo @@ -800,19 +800,19 @@ UID:c54c7930-51cc-5184-9dfb-5033e577b95e URL:https://emacsconf.org/2021/talks/project DTSTART:20211127T200300Z DTEND:20211127T201300Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nIn this talk I will present how we - use Org Mode at Shair.Tech for\nbudgeting\, project monitoring\, and invo - icing.\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\nprovide - s\, and reading here and there what other users do\, we\nimplemented an ef - fective workflow we have been using for nearly a\nyear\, now\, and with wh - ich we are very happy. Talk duration:\n\n–\;> 20 minutes seems to be - right (15 talk + questions)\n–\;> I can also make in 10 minutes\, b - y focusing the talk on\n budgeting (or monitoring) + 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) END:VEVENT BEGIN:VEVENT SUMMARY:Finding Your (In)voice: Emacs for Invoicing - Bala Ramadurai @@ -822,25 +822,25 @@ UID:c9870e10-2600-85a4-24fb-793dfc51164e URL:https://emacsconf.org/2021/talks/invoice DTSTART:20211127T201600Z DTEND:20211127T202600Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nYe Freelance warriors\, please lend me your I/O devices f - or 5 minutes.\n\nYour time is your money! Do you find it a pain to generat - e an invoice\,\nrecord the details into your accounting software and keep - track of\ntaxes and payments? You are not alone\, I found the whole invoic - e\nthingy to be extremely painful.\n\nBut worry not\, Emacs comes to our r - escue.\n\nMy talk will give you a basic intro on how to use org mode\, som - e embedded python code and file jugglery to generate stylistic and profess - ional invoices.\n\nWhat you will learn during the session:\n\n- How to t - rack your freelance time using orgmode\n- How to create the basic infras - tructure 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- pytho - n layer (I use spacemacs\, so whatever is the equivalent in your config)\n - - Some unnecessary Shakespearean references + 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 END:VEVENT BEGIN:VEVENT SUMMARY:Productivity Dashboards with Emacs and Kindle - Mehmet Tekman @@ -850,50 +850,50 @@ UID:e4e995c0-6e06-8544-a8c3-5f9a06c856fb URL:https://emacsconf.org/2021/talks/dashboard DTSTART:20211127T202900Z DTEND:20211127T203900Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nSince 2008\, Amazon have released a new Kindle devi - ce every year\,\nsupplanting each generation with a newer model that boast - s highly\npromoted incremental features which greatly devalues the price o - f\ntheir older models. These forgotten models are sold on Ebay and\nother - secondhand websites at highly discount prices by owners who\ndo not see th - e true potential of these devices: Kindles are\nexcellent high contrast lo - w-refresh display rate E-Ink devices\,\nwith Wifi capability\, that run em - bedded Linux in the\nbackground. Depending on the model\, an idle Kindle c - an last weeks\nbefore needing a recharge. This makes them ideal as passive - image\ndevices that can be configured easily using a few shell\nscripts. - 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 carefully d - isabling the software/bloatware that\ncomes with the device\, these Kindle - s have found new life as online\ndashboard devices which can fetch and dis - play information from the\ninternet at timely intervals.\n\nHere we descri - be a tool to control multiple Kindle devices with a\nsingle org-mode/shell - -based tool\, built initially to periodically\nserve updated Emacs Org-Age - nda views\, but later expanded to produce\nonline local weather reports an - d work calendar\, Emacs calendars\n(calfw\, org-gcal)\, daily dietary info - rmation (org-calories)\,\nOrg-Mode sparse TODO trees\, miscellaneous image - and text content\n(via imagemagick)\, small messages\, and much more.\n\n - In this talk\, we show how to configure multiple Kindles with any\ndesired - custom content\, following any daily/weekly schedule\, all\neasily manage - d from Emacs within a single Org-Mode file.\n\n\n\n# Outline\n\n- 5-10 m - inutes:\n\n 1-3 mins\n Talk about repurposing Kindles:\n\n - - Cheap second-hand wifi device\, hackable\n - Low-powered\, long b - attery life\, low refresh rate –\; perfect\n for a dashboard\ - n - Timely updated Org-Mode Agendas anyone?\n - Reference to - inspired projects (kindle-dashboard)\n\n 2-3 mins\n Generate - content\n\n - A static text+picture image easily generated with image - magick\n wrapper\n - An image of a sparse tree of org-mode TOD - O file\n - An image of another emacs view (e.g. Calfw\, or org-calori - es)\n - Show post-processing for optimizing image for Kindles\n\n - 1-2 mins\n Configuration in a single org-mode file\n\n - Def - ining Machines\n - Defining Commands to generate content\n - Def - ining Schedules to run Commands on multiple Machines at\n specific - points in the day\n\n 1-2 mins\n Export and Run:\n\n - Sh - ow exported shell configs and generated cronjobs\n - Witness multiple - Kindles producing desired content with wakeup\n timers + 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 END:VEVENT BEGIN:VEVENT SUMMARY:Emacs with Nyxt: extend your editor with the power of a Lisp browse @@ -904,25 +904,25 @@ UID:33776e08-e815-db94-971b-a151236e11be URL:https://emacsconf.org/2021/talks/nyxt DTSTART:20211127T204200Z DTEND:20211127T205200Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nIn 2021 browsers are essential if you u - se a computer. Even if Emacs\nusers love text as a format\, they may need - to shop and video call from\ntime to time (even more so in a pandemic!). S - ome of us modified their\nbrowsers to at least have the same keybindings a - s 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 you c - ould run\na REPL to extend your browser while browsing? What if you could - record\nmacros?! The browser exists: its name is Nyxt!\n\nIn this talk I w - ill share why it has great potential\, how you can\nintegrate it with Emac - s\, 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 talk!\ - n\nYou can learn more about this at: <https://github.com/ag91/emacs-with-n - yxt>\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 + 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 END:VEVENT BEGIN:VEVENT SUMMARY:On the design of text editors - Nicolas P. Rougier @@ -932,34 +932,34 @@ UID:86d4470a-8d19-7bd4-0c53-6aba1b49baef URL:https://emacsconf.org/2021/talks/design DTSTART:20211127T205500Z DTEND:20211127T210500Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nText editors are written by and for developers. They come\nwith - a large set of default and implicit choices in terms of layout\,\ntypograp - hy\, colorization and interaction that hardly change from one\neditor to t - he other. It is not clear if these implicit choices derive\nfrom the ignor - ance of alternatives or if they derive from developers'\nhabits\, reproduc - ing what they are used to. Durint this talk\, I will\ncharacterize these i - mplicit choices and illustrate what are some\nalternatives using GNU Emacs - .\n\n# Outline\n\n1. Review of a "modern" code editor (5mn)\n2. Introducti - on of an alternative using Emacs (5mn)\n\n## Links from the slides:\n\n* [ - Elegant Emacs](https://github.com/rougier/elegant-emacs) (https://github.c - om/rougier/elegant-emacs)\n* [On the Design of Text Editors](https://arxiv - .org/abs/2008.06030) (https://arxiv.org/abs/2008.06030)\n* [N Λ N O Emacs] - (https://github.com/rougier/nano-emacs) (https://github.com/rougier/nano-e - macs)\n* [svg-lib (ELPA)](https://elpa.gnu.org/packages/svg-lib.html) (htt - ps://elpa.gnu.org/packages/svg-lib.html)\n* [nano-theme (ELPA)](https://el - pa.gnu.org/packages/nano-theme.html) (https://elpa.gnu.org/packages/nano-t - heme.html)\n* [nano-modeline (ELPA)](https://elpa.gnu.org/packages/nano-mo - deline.html) (https://elpa.gnu.org/packages/nano-modeline.html)\n* [nano-a - genda (ELPA)](https://elpa.gnu.org/packages/nano-agenda.html) (https://elp - a.gnu.org/packages/nano-agenda.html)\n\n## Contact information\n* Contact - [nicolas.rougier@inria.fr](mailto:nicolas.rougier@inria.fr)\n* Follow my w - ork 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/) + 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/) END:VEVENT BEGIN:VEVENT SUMMARY:Emacs development updates - John Wiegley @@ -969,7 +969,7 @@ UID:59e4daca-1e46-9054-9573-9c91966d6987 URL:https://emacsconf.org/2021/talks/dev-update DTSTART:20211127T210900Z DTEND:20211127T211700Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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 @@ -982,34 +982,34 @@ UID:48a8580f-52ce-cc84-6a23-1eddf720ae02 URL:https://emacsconf.org/2021/talks/freedom DTSTART:20211127T212000Z DTEND:20211127T215800Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nThe theme will be "how Emacs empowered my softw - are freedom".\nI will outline the key moments in my transition to a GNU/Li - nux operating\nsystem and mark those which eventually contributed towards - me becoming\nan Emacs user\, maintainer of a—\;dare I say—\;po - pular package\, and\ncontributor to upstream Emacs (among others). By all - uding to personal\nexperiences\, I will draw generalisable insights and co - nnect them to what\nI believe are irreducible qualities of Emacs qua softw - are and Emacs as a\ncommunity of like-minded people. The talk will be the - oretical in\nnature: there won't be any code-related demonstration nor tec - hnical\nreferences that only people with a background in computer science - would\nlikely recognise. Personal anecdotes shall be tangential to the po - int\nand considered as ancillary to the thesis of what Emacs represents fr - om\nthe standpoint of software freedom and user empowerment. The\npresent - ation is intended for a general audience that is interested in\nGNU softwa - re in general and Emacs in particular. My formal educational\nbackground - as a social scientist (i.e. not a programmer) and later as a\nphilosopher - informs my approach to this topic.\n\nThe presentation shall be 40 minutes - long. Its text will be in essay\nform and shall be supplied as complemen - tary material to the video. The\nnotation will be in Org mode. I cannot - provide an outline in advance\,\nas it will most likely not be consistent - with the actual presentation.\nIf\, however\, this is absolutely required - for administrative purposes I\nshall furnish one regardless with the provi - so that I am in no way bound\nby it and thus reserve the right to modify i - t ahead of the main event. + 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. END:VEVENT BEGIN:VEVENT SUMMARY:Closing remarks day 1 @@ -1019,7 +1019,7 @@ UID:5287b003-f368-36c4-4f9b-8135734cad39 URL:https://emacsconf.org/2021/talks/day1-close DTSTART:20211127T220000Z DTEND:20211127T220500Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs conf.org/2021/talks/day1-close\n# Closing remarks day 1 END:VEVENT @@ -1031,7 +1031,7 @@ UID:d877a57a-14cf-a194-99c3-a344ecb24acc URL:https://emacsconf.org/2021/talks/day2-open DTSTART:20211128T140000Z DTEND:20211128T140500Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs conf.org/2021/talks/day2-open\n# Opening remarks day 2 END:VEVENT @@ -1043,18 +1043,18 @@ UID:35d1d9e4-dfdf-f254-6aab-7a466fbfaf09 URL:https://emacsconf.org/2021/talks/faster DTSTART:20211128T140500Z DTEND:20211128T142500Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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- Before optimizing\, benchmark first.\n- Different benchmarking a - pproaches.\n- Live evaluation\, step-debugging\, measuring from a debugg - er breakpoint.\n- How to determine if a function is expensive. How to pi - ck one from\n competing alternatives (cl-lib\, seq\, dash\, lean core). - \n- Print-benchmarking.\n- Byte-compiled code can give a very differen - t picture\, changing where\n the bottleneck is. How to quickly load a b - yte-compiled version.\n- Steps taken to speed up the Xref package recent - ly. + \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. END:VEVENT BEGIN:VEVENT SUMMARY:Tree-edit: Structural editing for Java\, Python\, C\, and beyond! - @@ -1065,33 +1065,33 @@ UID:599ef3fa-4c73-6c94-4953-75bbc7830681 URL:https://emacsconf.org/2021/talks/structural DTSTART:20211128T143000Z DTEND:20211128T144100Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nIn this talk\, I'll discuss a vis - ion for how writing code could be\, where the\nediting operations map dire - ctly to the primitives of the language itself -- and\nmy humble attempt of - implementing this vision. _tree-edit_ seeks to provides a\nstructural edi - ting plugin supporting conceivably any language with a tree-sitter\nparser - .\n\n**Structural editing does not have to be relegated to lisps or niche - DSLs.**\n\nI liken the state of code editing today to writing assembly. Th - e reason why\npeople like Python more than assembly is that for most purpo - ses\, the building\nblocks of the language are mismatched with our thought - process. We don't think\nin terms of registers and addresses\, we think i - n terms of variables\, functions\,\netc. So when we write and edit code\, - why do we edit in terms of deleting\,\ninserting\, replacing characters &# - x2013\; not wrapping\, inserting\, raising\,\ndeleting expressions and sta - tements?\n\nI'll also discuss the implementation of tree-edit\, which uses - a novel\ncombination of the fantastic\n[tree-sitter](https://github.com/e - macs-tree-sitter/elisp-tree-sitter) parser\nwith an embedded logic program - ming DSL ([miniKanren](http://minikanren.org/)\,\nusing elisp port [reazon - ](https://github.com/nickdrozd/reazon)) to power it's\nsyntax tree generat - ion.\n\nCheck out the GitHub repo [here](https://github.com/ethan-leba/tre - e-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 generator ( - Elevator pitch on miniKanren) + 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) END:VEVENT BEGIN:VEVENT SUMMARY:Self-Describing Smart DSL's: The Next Magits - Psionic @@ -1101,28 +1101,28 @@ UID:29d45a6f-9425-f5a4-bd23-297292e4ab7a URL:https://emacsconf.org/2021/talks/dsl DTSTART:20211128T144300Z DTEND:20211128T150300Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nWhen we begin programming\, the promise is to automate away repe - titive\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 grows\ - , we\nrun into the following issues:\n\n- As options pile up\, the intui - tion of simplicity is lost in helps and\nmanpages\n\n- Stateless operati - on has no idea what to do next and loses terseness\n- Frequent dispatch of - commands to interrogate state required for the\noperator to decide what a - ction to perform\n\n- Composition compounds with all of these issues\n\n - Magit has the UI trifecta of being terse\, intuitive\, and intelligent.\nM - agit's UI input library\, Transient\, is a standalone package for\ndevelop - ing more killer UI's\, and not just for CLI applications\, but\nalso for s - erver applications\, Emacs applications\, and Emacs itself.\n\nWhile Trans - ient's potential is to create the most highly productive\nUI's short of th - ought control\, going beyond simple command dispatchers\nrequires a deeper - dive. When we think like constructing a DSL for the\ntask and using tran - sient to input that DSL\, we get an intelligent\,\nself-describing modal p - rogramming system.\n\n\n# Outline\n\n- Updates to Transient documentation - and demos of API examples\n- Wrapping a custom CLI tool in Transient + 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 END:VEVENT BEGIN:VEVENT SUMMARY:"Yak-shaving to a UI framework" (/"Help! I accidentally yak-shaved @@ -1134,24 +1134,24 @@ UID:8f62e571-91da-bd14-e7c3-b445c7b19d23 URL:https://emacsconf.org/2021/talks/ui DTSTART:20211128T150600Z DTEND:20211128T151600Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nTui.el is a textual User Interface (UI) framework - for Emacs Lisp\nmodeled after the popular JavaScript 'React' framework. - This package\nimplements React Component API's with the goal of simplifyin - g\ndevelopment of interactive UI's for all Emacs users- regardless of\nthe - ir prior experience with React or web programming. Components\nprovide a - useful functional unit for constructing complex interfaces\ndeclaratively - and also eliminate much of the burden associated with\nupdating textual co - ntent as application state changes. This talk will\ncover use of the tui. - el API and its operation in a textual environment\nby implementing some ba - sic UI's.\n\n\n\n# Outline\n\n- 5-10 minutes:\n - Problem space: UI - implementation complexity.\n - API introduction: Displaying content\ - , Components.\n - Visual taste of dashboards and applications built w - ith tui. + 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. END:VEVENT BEGIN:VEVENT SUMMARY:Extending Emacs in Rust with Dynamic Modules - Tuấn-Anh Nguyễn @@ -1161,19 +1161,19 @@ UID:b073d391-6c37-6bf4-7afb-47edc79631a9 URL:https://emacsconf.org/2021/talks/rust DTSTART:20211128T151900Z DTEND:20211128T153900Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nDynamic module support has been available since Emacs 2 - 5. It can be\nused to extend Emacs with native libraries\, for performance - \,\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**safe** - alternative that is also a lot **more convenient**: writing these\ndynami - c modules in Rust.\n\n\n\n# Outline\n\n- Walking through creating **a sim - ple dynamic module** in\n Rust\, including setting up CI.\n- Going thr - ough and explaining the **available APIs**. + 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**. END:VEVENT BEGIN:VEVENT SUMMARY:Emacs Application Framework: A 2021 Update - Matthew Zeng @@ -1183,15 +1183,15 @@ UID:e7981936-6d72-93d4-8783-5ac64a0ae5bb URL:https://emacsconf.org/2021/talks/eaf DTSTART:20211128T154400Z DTEND:20211128T155400Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nEmacs Application Framework (EAF) is a customizable and exten - sible GUI\napplication framework that extends Emacs graphical capabilities - using\nPyQt5. There are many new but important updates since EmacsConf202 - 0\nlast year\, this talk will briefly go over them.\n\n\n\n# Outline\n\n- - 5-10 minutes: (brief description/outline) + 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) END:VEVENT BEGIN:VEVENT SUMMARY:Extending the "model" of Emacs to other applications - Laszlo Krajn @@ -1202,55 +1202,55 @@ UID:5e1baaaf-56a3-b5b4-31cb-5437cf465cf9 URL:https://emacsconf.org/2021/talks/model DTSTART:20211128T155800Z DTEND:20211128T160800Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nEmacs is a great operating environment i - n a sense that it provides consistency\nacross different tools and applica - tions within the Emacs ecosystem\, as well as\nexternal apps that can be i - ntegrated into it. It is also the most truly\nmalleable environment\, each - element of which can be adjusted or extended\,\ntherefore providing the u - ser with more power and freedom in personal computing.\nEmacs definitely c - an be considered one of greatest software products in\nexistence.\n\nAs a - non-programmer\, having had the chance to stumble upon Emacs a couple of\n - years 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 the l - ess technical\nfolks to join the party and gradually start to use Emacs fo - r writing documents\,\nwhether personal or work related\, manage tasks\, e - mails and potentially everything\nelse. The learning curve and difference - in approach\, however\, leaves some\npotential users too scared of the arc - ane interface even with all it's quirks and\nfeatures because it requires - at least some technical skills to understand and\nuse properly\, and does - 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 mod - el of Emacs\, it's focus on\nconsistency\, extensibility\, as well as it's - powerful interaction model can be\ncarried over to make modern interfaces - \, whether desktop or web applications\,\nthat would be designed with a go - al of reflecting the spirit of Emacs in terms of\nthe aforementioned featu - res it possesses\, and therefore enhance the capabilities\nof the Emacs\, - 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 personal we - b-interface for using modern task management tools\, chats\, emails\nand s - uch\, but from a UI defined by the user. The goal is to use it on a deskto - p\nor mobile\, locally or self-hosted on a server\, with support for touch - and\ngesture-based workflows\, while preserving the Emacs philosophy and - allowing to\nseamlessly switch between Emacs and its web extension\n\nThe - proposed solution is to integrate more of the modern tools with Emacs\,\nu - tilize Org-mode as a way to define application-specific parameters for the - se\ntools through Org properties\, and then utilize these parameters for m - aking a\nmodern local frontend that would enhance Emacs UI while allowing - to use external\ntools in a more personal and freedom respecting way (maki - ng the originals\nobsolete over time). The talk serves the purpose of invi - ting community members to\na discussion about how Emacs can become more mo - dern\, more approachable by people\nwho don't possess the neccessarry tech - nical skills to adjust it themselves\, but\nare keen to learn it\, and pot - entially how to attract more users to greater\nproductivity\, computer lit - eracy and the ideas of free software.\n\n\n\n# Outline\n\n- 5-10 minutes - \n - Introduction\n - Issues with most modern tools for work\n - - Issues with Emacs as a tool for work\n - In search for a hybrid - approach\n - User controlled web-apps\n - Opinions encouraged\n - - Contacts + 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 END:VEVENT BEGIN:VEVENT SUMMARY:Don't write that package! or: How I learned to stop worrying and lo @@ -1261,28 +1261,28 @@ UID:4cd6de26-cf48-95c4-9d3b-28895a43ec53 URL:https://emacsconf.org/2021/talks/devel DTSTART:20211128T161100Z DTEND:20211128T163100Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nWe need a successfu - l 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 and c - ustomize. There is so much great experimentation\nand work going on out t - here in the wider Emacs community\, but we would\nbe even better off if mo - re of that could go into Emacs itself.\n\nEmacs' greatest strength is unfo - rtunately sometimes also its greatest\nweakness: it is *too* hackable.\n\n - On occasion\, people out there add stuff to their Init file to fix this\no - r that annoyance\, or even bug. The more ambitious might go on to\npackag - e 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 that - same\nproblem or annoyance\, and would benefit from your solution?\n\nIt i - s sometimes perceived as hard to contribute to Emacs core. I want\nto enc - ourage more people to get involved\, and show that the barrier to\nentry i - s really not that high. If I can do it\, you can do it too!\n\nSo should - you really write that package\, or should you stop worrying and\nlearn to - love emacs-devel? Listen to my talk to find out more! + 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! END:VEVENT BEGIN:VEVENT SUMMARY:Turbo Bindat - Stefan Monnier @@ -1292,20 +1292,20 @@ UID:49a35f05-b71f-1d14-2343-a6638bec0d08 URL:https://emacsconf.org/2021/talks/bindat DTSTART:20211128T163600Z DTEND:20211128T170600Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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# Table 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\, EM - MS\, and\ncpio-mode. Its implementation was repeatedly caught harassing ha - pless\nkitten while at the same time providing poor service slowly. For\nE - macs-28\, Bindat was rewritten so as to make it more efficient and\nflexib - le 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 proble - ms\n 5 min: Present the new design\n 5 min: Examples of what can be - done with it + 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 END:VEVENT BEGIN:VEVENT SUMMARY:Emacs Lisp native compiler\, current status and future developments @@ -1316,20 +1316,20 @@ UID:1ddbe380-b4f3-2b84-3cc3-9e799536db8e URL:https://emacsconf.org/2021/talks/native DTSTART:20211128T174000Z DTEND:20211128T182000Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nEmacs Lisp (Elisp) is the Lisp - dialect used by the Emacs text editor\nfamily. GNU Emacs is traditionally - capable of executing Elisp code\neither interpreted or byte-interpreted a - fter 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 main E - macs development line allow for\nautomatically compiling and executing Eli - sp as native code.\n\nDuring the presentation I'll touch on:\n\n- design - goals\n- compiler and runtime design and implementation\n- performanc - e implications\n- upstream process\n- area of improvements and future - developments\n\nFormat: 40 minutes + 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 END:VEVENT BEGIN:VEVENT SUMMARY:Old McCarthy Had a Form - Ian Eure @@ -1339,18 +1339,18 @@ UID:5947c3e9-93c1-1014-7ffb-aa0e0097e3e4 URL:https://emacsconf.org/2021/talks/form DTSTART:20211128T182700Z DTEND:20211128T183700Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nMost prac - tical languages are multi-paradigm\, offering several\nabstractions for th - e programmer. But did you know that Emacs Lisp\ncomes with a powerful sys - tem for object-oriented programming? Join me\nfor a discussion of EIEIO\, - and learn how it can help you write more\nmodular\, flexible Emacs Lisp.\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 - Furthe - r reading + 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 END:VEVENT BEGIN:VEVENT SUMMARY:Test blocks - Eduardo Ochs @@ -1360,37 +1360,37 @@ UID:5e162d34-ea19-8544-b693-dd6da0e885cd URL:https://emacsconf.org/2021/talks/test DTSTART:20211128T184100Z DTEND:20211128T184600Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nIn this presentat - ion I will show an idea that feels completely obvious\nonce we see it\, bu - t that only occured to me after after using Emacs\nand eev as my main inte - rface to the computer for more than 20 years.\nTake any interpreted langua - ge that supports multi-line comments\, and\nwhose interpreter can be run i - n an Emacs buffer - for example Lua\,\nHaskell\, Python\, or Julia\; let's - say just "Lua" from here on for\nsimplicity. So: suppose that we have a L - ua script that we wrote\, that\nis called "foo.lua" and that defines lots - 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 eepitc - h block that when\nexecuted starts a Lua interpreter\, loads the script fo - o.lua (by\nrunning 'dofile "foo.lua"')\, and then has several tests for th - at class\nand its methods\; and we can put another block with tests like t - hat\nafter the class Bletch\, and other blocks after some functions. Eepit - ch\nallows sending these tests line by line to the Lua interpreter by\ntyp - ing <f8\\> on each line that we want to send\, and this lets us create\nte - sts that are very easy to understand even without writing comments\;\nthis - gives us a very quick way to document code by executable tests\,\nthat is - super-great for experimental code that is still going to\nchange a lot be - fore running the risk of being read by other people.\n\nThese multi-line c - omments with eepitch blocks that run an interpreter\nand make it load the - current file are called "test blocks". The\ncommand \\`M-x eeit' inserts a - test block at point\, using the major mode\nto decide the right syntax to - use for the multi-line comments and for\nthe "dofile". We can configure t - he 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 blocks - to more languages (or\, more\nprecisely: to more major modes).\n\nEduardo - Ochs <http://angg.twu.net/emacsconf2021.html> + 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> END:VEVENT BEGIN:VEVENT SUMMARY:Let's talk about bug trackers - Bastien Guerry @@ -1400,14 +1400,14 @@ UID:51023225-018f-cf24-9d73-3c267907c13e URL:https://emacsconf.org/2021/talks/bug DTSTART:20211128T184900Z DTEND:20211128T190900Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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 - \nFor 17 years\, the Org developers didn't use a bug tracker\,\nshamelessl - y failing the Joel Spolsky test. Why was it "good enough"?\nWhy was it wr - ong? Why did we move to Woof!? Why Woof! is not a bug\ntracker?\n\n- 2 - 0 minutes + \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 END:VEVENT BEGIN:VEVENT SUMMARY:Perso-Arabic Input Methods And Making More Emacs Apps BIDI Aware - @@ -1418,65 +1418,65 @@ UID:1407591a-29fd-3f64-1beb-01dea6e9d7d2 URL:https://emacsconf.org/2021/talks/bidi DTSTART:20211128T191600Z DTEND:20211128T193600Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nEmacs is a multilingual user environment. - A true multilingual editor must\nsupport bidirectionality and shaping of c - haracters. Perso-Arabic scripts require\nboth of these features.\n\nStarti - ng with Emacs 24\, full native bidi\n(bidirectional) support became availa - ble. For\nmany years prior to that Unicode support was\navailable and by - around year 2000\, reasonable\nopen-source shaping libraries were also ava - ilable.\n\nWith these in place at around 2012\, I developed\ntwo Persian i - nput methods for emacs. These input\nmethods or variations of them can als - o be used for\nArabic and other Perso-Arabic scripts.\n\nWith all of these - in place\, Emacs has now become\nthe ne plus ultra Libre-Halaal and Convi - vial usage\nenvironment for Perso-Arabic users.\n\nSince emacs comes loade - d with everything (Gnus\nfor email\, Bbdb for address books\, XeLaTeX mode - s\nfor typesetting\, org-mode for organization\, spell\ncheckers\, complet - ion systems\, calendar\, etc.)\, all basic\ncomputing and communication ne - eds of Perso-Arabic\nusers can be addressed in one place and\ncohesively.\ - 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 input - methods. With an emphasis on "Banan\nMulti-Character (Reverse) Translitera - tion Persian Input Method". The\nsoftware is part of base emacs distributi - on. Full documentation is available\nat:\n\n Persian Input Metho - ds\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. Emacs - 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 - Existing e - macs 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 bidi on - display.\n - Use of Persian text for Persian (solar) calendar.\n - - Use of Arabic text for Muslem (lunar) calendar.\n\n- AUCTeX: Persia - n typesetting with XeLaTeX\n - Option of having right-to-left Perso- - Arabic aliases for all latex commands.\n\nReferences:\n\n - Persian Inp - ut Methods:\n <http://mohsen.1.banan.byname.net/PLPC/120036>\n < - http://www.persoarabic.org/PLPC/120036> -- Persian Input Methods Access Pa - ge\n <http://www.persoarabic.org> -- Various Perso-Arabic resources\n - <http://www.freeprotocols.org/Repub/fpf-isiri-6219> -- Re-Publicatio - n Of\n Persian Information Interchange and Display Mechanism\, us - ing Unicode\n <https://github.com/bx-blee/persian-input-method> -- Gi - t repo for\n persian.el -- Quail package for inputting Persian/Fa - rsi keyboards\n\n - BIDI:\n <http://www.unicode.org/reports/tr9/> - -- Annex #9 of the Unicode standard\n <https://www.gnu.org/software/e - macs/manual/html_node/elisp/Bidirectional-Display.html>\n Emacs B - idirectional Display\n\n - Blee and Persian-Blee:\n <https://githu - b.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 Nature o - f Polyexistentials:\n Basis for Abolishment of The Western Inte - llectual Property Rights Regime\n <http://mohsen.1.banan.byname.net/P - LPC/120039> -- Defining The Libre-Halaal Label\n\n - Mohsen BANAN -- مح - سن بنان:\n <http://mohsen.1.banan.byname.net/> -- Globish\n <htt - p://mohsen.1.banan.byname.net/persian> -- Farsi\n <http://mohsen.1.ba - nan.byname.net/french> -- French + \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 END:VEVENT BEGIN:VEVENT SUMMARY:Moldable Emacs\, a step towards sustainable software - Andrea @@ -1486,28 +1486,28 @@ UID:3364aedb-a496-5c64-5383-b0080afa6d7b URL:https://emacsconf.org/2021/talks/mold DTSTART:20211128T194100Z DTEND:20211128T195100Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nWe could learn about things better. Mountains of knowle - dge 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\nKnowledge - (web\, software\, books) keeps growing faster and faster! This\nis not sus - tainable: we cannot keep up with it! What if we repeat the\nerror of someb - ody else\, only because it would take too much reading to\nknow? What if t - hat knowledge is in some code we work with everyday?\n\nMoldable developme - nt is a paradigm shift that attempts to solve this\nproblem. In a gist\, t - he 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 edito - r moldable!\n\nThis talk shows my progress in making Emacs closer to such - a tool. We\nare going to see how we can mold structured (and maybe even na - tural)\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 qui - cker way to learn from our digital\nworld!\n\nYou can learn more about thi - s at: <https://github.com/ag91/moldable-emacs>\n\n\n\n# Outline\n\n- 5-1 - 0 minutes: quick demo of moldable-emacs + /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 END:VEVENT BEGIN:VEVENT SUMMARY:CLEDE the Common Lisp Emacs Development Environment. - Fermin MF @@ -1517,20 +1517,20 @@ UID:daf3570b-3df3-9db4-a1f3-ce98d9863717 URL:https://emacsconf.org/2021/talks/clede DTSTART:20211128T195500Z DTEND:20211128T201500Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nI've been developing a package that helps with the d - evelopment of\nCommon Lisp's software\,\nit's uses the internal semantic f - ramework\, it has a custom reader\nand integration for\ncommon Emacs packa - ges (like Sly and the internal inferior-lisp-mode).\n\nThe idea is to supp - ly features that other language with and static\nanalyzer have\,\nlike ref - actoring and code generation.\n\nFor more details: <https://gitlab.com/sas - anidas/clede>\n\n- 20 minutes:\n It seems like not too much people kn - ows 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. + 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. END:VEVENT BEGIN:VEVENT SUMMARY:Imaginary Programming - Shane Mulligan @@ -1540,31 +1540,31 @@ UID:f03ae971-4d2b-ccc4-2643-4ae2391ce1ab URL:https://emacsconf.org/2021/talks/imaginary DTSTART:20211128T202200Z DTEND:20211128T203300Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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 - Imaginary Programming (IP) is both methodology and paradigm. It is an\next - ension of literate programming and a way of creating software without\nthe - use of imperative\, functional or even declarative code. Yet IP employs\n - all disciplines to achieve the miraculous. The only contingency is on one\ - nor more language models\, known as foundation models. The real value of I - P\nis not found by abandoning sound logic altogether\, but in weaving the - real\nwith the imaginary. The future of imaginary programming is one in wh - ich\nalmost all of computing is inferred. I have built a suite of tools ba - sed on\nemacs for interfacing real programming languages with imaginary on - es\; all\nof this in order to demonstrate what I mean\; a ‘complex’ termin - al that lets\nyou imagine what happens no matter how nested you are within - interpreters\,\nan example-oriented language\, a file format that encodes - the provenance of\ntext and a library for imaginary functional programmin - g primitives called\niLambda. It is important to recognise IP because\, fo - r lack of a better\nterm\, it has far-reaching implications for intellectu - al 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\, fo - llowed by\n - a demonstration of iLambda.\n - iλ\, a family - of imaginary programming libraries\n <https://mullikine.github.io/p - osts/designing-an-imaginary-programming-ip-library-for-emacs/>\n\n\n\nIRC - libertyprime at #emacs on libera\n\nShane Mulligan + \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 END:VEVENT BEGIN:VEVENT SUMMARY:How to build an Emacs - Fermin MF @@ -1574,21 +1574,21 @@ UID:27595637-b6b9-f764-805b-ff1b7f009006 URL:https://emacsconf.org/2021/talks/build DTSTART:20211128T203600Z DTEND:20211128T205600Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nThis is a - deep dive in the Emacs philosophical and technical\naspect on what makes - our beloved GNU Emacs\nwhat it it. It's also a talk about the early LISP m - achines and\nfascinating were those days of experimentation and engineerin - g.\n\nIt will continue with the Emacs benefits/trade-offs from an\nuser/de - veloper stand points\, what things can be improved and\nwhat can be an hyp - othetical path on how to build a software that\ncan also be called Emacs.\ - n\nAs a last part\, I'll talk about CEDAR\, an Emacs that I've been\ndevel - oping in Common Lisp\, the project goals\nand the challenges.\n\nFor more - details about CEDAR: <https://gitlab.com/sasanidas/cedar>\n\n- 40 minute - s:\n A dive into the Emacs/Lisp machines history\, what makes GNU Emacs - \n an Emacs and how you can build an 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. END:VEVENT BEGIN:VEVENT SUMMARY:M-x Forever: Why Emacs will outlast text editor trends - David Wils @@ -1599,21 +1599,21 @@ UID:80d1ad02-5fe4-03b4-c573-17ea6cdb61aa URL:https://emacsconf.org/2021/talks/forever DTSTART:20211128T210300Z DTEND:20211128T214300Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z 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\nThe computer software industry has seen many - "popular" text editors come\nand go\, often due to the mercurial fashions - of software development. In\nthis talk\, we'll take a look at why popular - editors fade and the\nspecific aspects of Emacs that will ensure it remai - ns relevant\nregardless of mainstream popularity.\n\n\n\n# Outline\n\n- Di - scuss the core thesis\, the features that make Emacs\n desirable for long - -term use (extensibility\, day-to-day 'life' features)\n\n- Include more b - ackground on the text editor landscape and\n how the scope of various edi - tors is more narrow and doesn't compare to Emacs.\n\n- Talk about specific - instances where editors were popular\, fell out\n of popularity\, and wh - y (due to changing fashions\, not usually\n better features). + 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). END:VEVENT BEGIN:VEVENT SUMMARY:Closing remarks day 2 @@ -1623,7 +1623,7 @@ UID:828e7c62-8430-f1a4-431b-63c308d58688 URL:https://emacsconf.org/2021/talks/day2-close DTSTART:20211128T215000Z DTEND:20211128T220000Z -DTSTAMP:20211113T144501Z +DTSTAMP:20211113T170719Z DESCRIPTION: Times are approximate and will probably change.\nhttps://emacs conf.org/2021/talks/day2-close\n# Closing remarks day 2 END:VEVENT diff --git a/2021/info/babel-schedule.md b/2021/info/babel-schedule.md index 4321b394..71671f40 100644 --- a/2021/info/babel-schedule.md +++ b/2021/info/babel-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Prerecorded video received, waiting for captions +Duration: 10 minutes +Friendly URL: <a href="/2021/talks/babel">/2021/talks/babel</a> -Prerecorded video received, waiting for captions +Saturday, Nov 27 2021, ~ 2:38 PM - 2:48 PM EST +Saturday, Nov 27 2021, ~11:38 AM - 11:48 AM PST +Saturday, Nov 27 2021, ~ 7:38 PM - 7:48 PM UTC +Saturday, Nov 27 2021, ~ 8:38 PM - 8:48 PM CET +Sunday, Nov 28 2021, ~ 3:38 AM - 3:48 AM +08 -# Schedule - -Allocated 10 minutes - - - -Friendly URL: <a href="/2021/talks/babel">/2021/talks/babel</a> +# Description diff --git a/2021/info/bidi-schedule.md b/2021/info/bidi-schedule.md index e810f15c..c536f9e3 100644 --- a/2021/info/bidi-schedule.md +++ b/2021/info/bidi-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Waiting for speaker to send prerecorded video +Duration: 20 minutes +Friendly URL: <a href="/2021/talks/bidi">/2021/talks/bidi</a> -Waiting for speaker to send prerecorded video +Sunday, Nov 28 2021, ~ 2:16 PM - 2:36 PM EST +Sunday, Nov 28 2021, ~11:16 AM - 11:36 AM PST +Sunday, Nov 28 2021, ~ 7:16 PM - 7:36 PM UTC +Sunday, Nov 28 2021, ~ 8:16 PM - 8:36 PM CET +Monday, Nov 29 2021, ~ 3:16 AM - 3:36 AM +08 -# Schedule - -Allocated 20 minutes - - - -Friendly URL: <a href="/2021/talks/bidi">/2021/talks/bidi</a> +# Description diff --git a/2021/info/bindat-schedule.md b/2021/info/bindat-schedule.md index df2d268a..f27075d5 100644 --- a/2021/info/bindat-schedule.md +++ b/2021/info/bindat-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Prerecorded video received, waiting for captions +Duration: 30 minutes +Friendly URL: <a href="/2021/talks/bindat">/2021/talks/bindat</a> -Prerecorded video received, waiting for captions +Sunday, Nov 28 2021, ~11:36 AM - 12:06 PM EST +Sunday, Nov 28 2021, ~ 8:36 AM - 9:06 AM PST +Sunday, Nov 28 2021, ~ 4:36 PM - 5:06 PM UTC +Sunday, Nov 28 2021, ~ 5:36 PM - 6:06 PM CET +Monday, Nov 29 2021, ~12:36 AM - 1:06 AM +08 -# Schedule - -Allocated 30 minutes - - - -Friendly URL: <a href="/2021/talks/bindat">/2021/talks/bindat</a> +# Description diff --git a/2021/info/borg-schedule.md b/2021/info/borg-schedule.md index 77fc3ecc..32a07c7d 100644 --- a/2021/info/borg-schedule.md +++ b/2021/info/borg-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Captions added to video +Duration: 8 minutes +Friendly URL: <a href="/2021/talks/borg">/2021/talks/borg</a> -Captions added to video +Saturday, Nov 27 2021, ~10:36 AM - 10:44 AM EST +Saturday, Nov 27 2021, ~ 7:36 AM - 7:44 AM PST +Saturday, Nov 27 2021, ~ 3:36 PM - 3:44 PM UTC +Saturday, Nov 27 2021, ~ 4:36 PM - 4:44 PM CET +Saturday, Nov 27 2021, ~11:36 PM - 11:44 PM +08 -# Schedule - -Allocated 8 minutes - - - -Friendly URL: <a href="/2021/talks/borg">/2021/talks/borg</a> +# Description diff --git a/2021/info/bug-schedule.md b/2021/info/bug-schedule.md index c7e96a66..635fc073 100644 --- a/2021/info/bug-schedule.md +++ b/2021/info/bug-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Waiting for speaker to send prerecorded video +Duration: 20 minutes +Friendly URL: <a href="/2021/talks/bug">/2021/talks/bug</a> -Waiting for speaker to send prerecorded video +Sunday, Nov 28 2021, ~ 1:49 PM - 2:09 PM EST +Sunday, Nov 28 2021, ~10:49 AM - 11:09 AM PST +Sunday, Nov 28 2021, ~ 6:49 PM - 7:09 PM UTC +Sunday, Nov 28 2021, ~ 7:49 PM - 8:09 PM CET +Monday, Nov 29 2021, ~ 2:49 AM - 3:09 AM +08 -# Schedule - -Allocated 20 minutes - - - -Friendly URL: <a href="/2021/talks/bug">/2021/talks/bug</a> +# Description diff --git a/2021/info/build-schedule.md b/2021/info/build-schedule.md index 0184a782..a4939af0 100644 --- a/2021/info/build-schedule.md +++ b/2021/info/build-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Waiting for speaker to send prerecorded video +Duration: 20 minutes +Friendly URL: <a href="/2021/talks/build">/2021/talks/build</a> -Waiting for speaker to send prerecorded video +Sunday, Nov 28 2021, ~ 3:36 PM - 3:56 PM EST +Sunday, Nov 28 2021, ~12:36 PM - 12:56 PM PST +Sunday, Nov 28 2021, ~ 8:36 PM - 8:56 PM UTC +Sunday, Nov 28 2021, ~ 9:36 PM - 9:56 PM CET +Monday, Nov 29 2021, ~ 4:36 AM - 4:56 AM +08 -# Schedule - -Allocated 20 minutes - - - -Friendly URL: <a href="/2021/talks/build">/2021/talks/build</a> +# Description diff --git a/2021/info/clede-schedule.md b/2021/info/clede-schedule.md index d498d988..a86ecedd 100644 --- a/2021/info/clede-schedule.md +++ b/2021/info/clede-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Waiting for speaker to send prerecorded video +Duration: 20 minutes +Friendly URL: <a href="/2021/talks/clede">/2021/talks/clede</a> -Waiting for speaker to send prerecorded video +Sunday, Nov 28 2021, ~ 2:55 PM - 3:15 PM EST +Sunday, Nov 28 2021, ~11:55 AM - 12:15 PM PST +Sunday, Nov 28 2021, ~ 7:55 PM - 8:15 PM UTC +Sunday, Nov 28 2021, ~ 8:55 PM - 9:15 PM CET +Monday, Nov 29 2021, ~ 3:55 AM - 4:15 AM +08 -# Schedule - -Allocated 20 minutes - - - -Friendly URL: <a href="/2021/talks/clede">/2021/talks/clede</a> +# Description diff --git a/2021/info/cs-schedule.md b/2021/info/cs-schedule.md index 1c7d7df0..e5f3dbd3 100644 --- a/2021/info/cs-schedule.md +++ b/2021/info/cs-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Waiting for speaker to send prerecorded video +Duration: 10 minutes +Friendly URL: <a href="/2021/talks/cs">/2021/talks/cs</a> -Waiting for speaker to send prerecorded video +Saturday, Nov 27 2021, ~ 1:01 PM - 1:11 PM EST +Saturday, Nov 27 2021, ~10:01 AM - 10:11 AM PST +Saturday, Nov 27 2021, ~ 6:01 PM - 6:11 PM UTC +Saturday, Nov 27 2021, ~ 7:01 PM - 7:11 PM CET +Sunday, Nov 28 2021, ~ 2:01 AM - 2:11 AM +08 -# Schedule - -Allocated 10 minutes - - - -Friendly URL: <a href="/2021/talks/cs">/2021/talks/cs</a> +# Description diff --git a/2021/info/dashboard-schedule.md b/2021/info/dashboard-schedule.md index ca03cecc..49ef0aef 100644 --- a/2021/info/dashboard-schedule.md +++ b/2021/info/dashboard-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Captions added to video +Duration: 10 minutes +Friendly URL: <a href="/2021/talks/dashboard">/2021/talks/dashboard</a> -Captions added to video +Saturday, Nov 27 2021, ~ 3:29 PM - 3:39 PM EST +Saturday, Nov 27 2021, ~12:29 PM - 12:39 PM PST +Saturday, Nov 27 2021, ~ 8:29 PM - 8:39 PM UTC +Saturday, Nov 27 2021, ~ 9:29 PM - 9:39 PM CET +Sunday, Nov 28 2021, ~ 4:29 AM - 4:39 AM +08 -# Schedule - -Allocated 10 minutes - - - -Friendly URL: <a href="/2021/talks/dashboard">/2021/talks/dashboard</a> +# Description diff --git a/2021/info/day1-close-schedule.md b/2021/info/day1-close-schedule.md index 8462497c..58b1f0e5 100644 --- a/2021/info/day1-close-schedule.md +++ b/2021/info/day1-close-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Will be live +Duration: 5 minutes +Friendly URL: <a href="/2021/talks/day1-close">/2021/talks/day1-close</a> -Will be live +Saturday, Nov 27 2021, ~ 5:00 PM - 5:05 PM EST +Saturday, Nov 27 2021, ~ 2:00 PM - 2:05 PM PST +Saturday, Nov 27 2021, ~10:00 PM - 10:05 PM UTC +Saturday, Nov 27 2021, ~11:00 PM - 11:05 PM CET +Sunday, Nov 28 2021, ~ 6:00 AM - 6:05 AM +08 -# Schedule - -Allocated 5 minutes - - - -Friendly URL: <a href="/2021/talks/day1-close">/2021/talks/day1-close</a> +# Description diff --git a/2021/info/day1-open-schedule.md b/2021/info/day1-open-schedule.md index 1a11844b..d53731ed 100644 --- a/2021/info/day1-open-schedule.md +++ b/2021/info/day1-open-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Will be live +Duration: 5 minutes +Friendly URL: <a href="/2021/talks/day1-open">/2021/talks/day1-open</a> -Will be live +Saturday, Nov 27 2021, ~ 9:00 AM - 9:05 AM EST +Saturday, Nov 27 2021, ~ 6:00 AM - 6:05 AM PST +Saturday, Nov 27 2021, ~ 2:00 PM - 2:05 PM UTC +Saturday, Nov 27 2021, ~ 3:00 PM - 3:05 PM CET +Saturday, Nov 27 2021, ~10:00 PM - 10:05 PM +08 -# Schedule - -Allocated 5 minutes - - - -Friendly URL: <a href="/2021/talks/day1-open">/2021/talks/day1-open</a> +# Description diff --git a/2021/info/day2-close-schedule.md b/2021/info/day2-close-schedule.md index c2a6785e..52098ef8 100644 --- a/2021/info/day2-close-schedule.md +++ b/2021/info/day2-close-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Will be live +Duration: 10 minutes +Friendly URL: <a href="/2021/talks/day2-close">/2021/talks/day2-close</a> -Will be live +Sunday, Nov 28 2021, ~ 4:50 PM - 5:00 PM EST +Sunday, Nov 28 2021, ~ 1:50 PM - 2:00 PM PST +Sunday, Nov 28 2021, ~ 9:50 PM - 10:00 PM UTC +Sunday, Nov 28 2021, ~10:50 PM - 11:00 PM CET +Monday, Nov 29 2021, ~ 5:50 AM - 6:00 AM +08 -# Schedule - -Allocated 10 minutes - - - -Friendly URL: <a href="/2021/talks/day2-close">/2021/talks/day2-close</a> +# Description diff --git a/2021/info/day2-open-schedule.md b/2021/info/day2-open-schedule.md index d2b465b2..d274a43e 100644 --- a/2021/info/day2-open-schedule.md +++ b/2021/info/day2-open-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Will be live +Duration: 5 minutes +Friendly URL: <a href="/2021/talks/day2-open">/2021/talks/day2-open</a> -Will be live +Sunday, Nov 28 2021, ~ 9:00 AM - 9:05 AM EST +Sunday, Nov 28 2021, ~ 6:00 AM - 6:05 AM PST +Sunday, Nov 28 2021, ~ 2:00 PM - 2:05 PM UTC +Sunday, Nov 28 2021, ~ 3:00 PM - 3:05 PM CET +Sunday, Nov 28 2021, ~10:00 PM - 10:05 PM +08 -# Schedule - -Allocated 5 minutes - - - -Friendly URL: <a href="/2021/talks/day2-open">/2021/talks/day2-open</a> +# Description diff --git a/2021/info/design-schedule.md b/2021/info/design-schedule.md index 02e46d84..20976356 100644 --- a/2021/info/design-schedule.md +++ b/2021/info/design-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Prerecorded video received, waiting for captions +Duration: 10 minutes +Friendly URL: <a href="/2021/talks/design">/2021/talks/design</a> -Prerecorded video received, waiting for captions +Saturday, Nov 27 2021, ~ 3:55 PM - 4:05 PM EST +Saturday, Nov 27 2021, ~12:55 PM - 1:05 PM PST +Saturday, Nov 27 2021, ~ 8:55 PM - 9:05 PM UTC +Saturday, Nov 27 2021, ~ 9:55 PM - 10:05 PM CET +Sunday, Nov 28 2021, ~ 4:55 AM - 5:05 AM +08 -# Schedule - -Allocated 10 minutes - - - -Friendly URL: <a href="/2021/talks/design">/2021/talks/design</a> +# Description diff --git a/2021/info/dev-update-schedule.md b/2021/info/dev-update-schedule.md index ea7bf65d..e82de787 100644 --- a/2021/info/dev-update-schedule.md +++ b/2021/info/dev-update-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Captions added to video +Duration: 8 minutes +Friendly URL: <a href="/2021/talks/dev-update">/2021/talks/dev-update</a> -Captions added to video +Saturday, Nov 27 2021, ~ 4:09 PM - 4:17 PM EST +Saturday, Nov 27 2021, ~ 1:09 PM - 1:17 PM PST +Saturday, Nov 27 2021, ~ 9:09 PM - 9:17 PM UTC +Saturday, Nov 27 2021, ~10:09 PM - 10:17 PM CET +Sunday, Nov 28 2021, ~ 5:09 AM - 5:17 AM +08 -# Schedule - -Allocated 8 minutes - - - -Friendly URL: <a href="/2021/talks/dev-update">/2021/talks/dev-update</a> +# Description diff --git a/2021/info/devel-schedule.md b/2021/info/devel-schedule.md index 929e26d9..4961c85f 100644 --- a/2021/info/devel-schedule.md +++ b/2021/info/devel-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Waiting for speaker to send prerecorded video +Duration: 20 minutes +Friendly URL: <a href="/2021/talks/devel">/2021/talks/devel</a> -Waiting for speaker to send prerecorded video +Sunday, Nov 28 2021, ~11:11 AM - 11:31 AM EST +Sunday, Nov 28 2021, ~ 8:11 AM - 8:31 AM PST +Sunday, Nov 28 2021, ~ 4:11 PM - 4:31 PM UTC +Sunday, Nov 28 2021, ~ 5:11 PM - 5:31 PM CET +Monday, Nov 29 2021, ~12:11 AM - 12:31 AM +08 -# Schedule - -Allocated 20 minutes - - - -Friendly URL: <a href="/2021/talks/devel">/2021/talks/devel</a> +# Description diff --git a/2021/info/dsl-schedule.md b/2021/info/dsl-schedule.md index 4340314a..51716e97 100644 --- a/2021/info/dsl-schedule.md +++ b/2021/info/dsl-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Waiting for speaker to send prerecorded video +Duration: 20 minutes +Friendly URL: <a href="/2021/talks/dsl">/2021/talks/dsl</a> -Waiting for speaker to send prerecorded video +Sunday, Nov 28 2021, ~ 9:43 AM - 10:03 AM EST +Sunday, Nov 28 2021, ~ 6:43 AM - 7:03 AM PST +Sunday, Nov 28 2021, ~ 2:43 PM - 3:03 PM UTC +Sunday, Nov 28 2021, ~ 3:43 PM - 4:03 PM CET +Sunday, Nov 28 2021, ~10:43 PM - 11:03 PM +08 -# Schedule - -Allocated 20 minutes - - - -Friendly URL: <a href="/2021/talks/dsl">/2021/talks/dsl</a> +# Description diff --git a/2021/info/eaf-schedule.md b/2021/info/eaf-schedule.md index fb7fb554..d71491f5 100644 --- a/2021/info/eaf-schedule.md +++ b/2021/info/eaf-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Waiting for speaker to send prerecorded video +Duration: 10 minutes +Friendly URL: <a href="/2021/talks/eaf">/2021/talks/eaf</a> -Waiting for speaker to send prerecorded video +Sunday, Nov 28 2021, ~10:44 AM - 10:54 AM EST +Sunday, Nov 28 2021, ~ 7:44 AM - 7:54 AM PST +Sunday, Nov 28 2021, ~ 3:44 PM - 3:54 PM UTC +Sunday, Nov 28 2021, ~ 4:44 PM - 4:54 PM CET +Sunday, Nov 28 2021, ~11:44 PM - 11:54 PM +08 -# Schedule - -Allocated 10 minutes - - - -Friendly URL: <a href="/2021/talks/eaf">/2021/talks/eaf</a> +# Description diff --git a/2021/info/erg-schedule.md b/2021/info/erg-schedule.md index f26d9b74..b0dd648b 100644 --- a/2021/info/erg-schedule.md +++ b/2021/info/erg-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Captions added to video +Duration: 15 minutes +Friendly URL: <a href="/2021/talks/erg">/2021/talks/erg</a> -Captions added to video +Saturday, Nov 27 2021, ~12:43 PM - 12:58 PM EST +Saturday, Nov 27 2021, ~ 9:43 AM - 9:58 AM PST +Saturday, Nov 27 2021, ~ 5:43 PM - 5:58 PM UTC +Saturday, Nov 27 2021, ~ 6:43 PM - 6:58 PM CET +Sunday, Nov 28 2021, ~ 1:43 AM - 1:58 AM +08 -# Schedule - -Allocated 15 minutes - - - -Friendly URL: <a href="/2021/talks/erg">/2021/talks/erg</a> +# Description diff --git a/2021/info/exec-schedule.md b/2021/info/exec-schedule.md index f1f8d197..788e9a78 100644 --- a/2021/info/exec-schedule.md +++ b/2021/info/exec-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Prerecorded video received, waiting for captions +Duration: 8 minutes +Friendly URL: <a href="/2021/talks/exec">/2021/talks/exec</a> -Prerecorded video received, waiting for captions +Saturday, Nov 27 2021, ~ 1:40 PM - 1:48 PM EST +Saturday, Nov 27 2021, ~10:40 AM - 10:48 AM PST +Saturday, Nov 27 2021, ~ 6:40 PM - 6:48 PM UTC +Saturday, Nov 27 2021, ~ 7:40 PM - 7:48 PM CET +Sunday, Nov 28 2021, ~ 2:40 AM - 2:48 AM +08 -# Schedule - -Allocated 8 minutes - - - -Friendly URL: <a href="/2021/talks/exec">/2021/talks/exec</a> +# Description diff --git a/2021/info/faster-schedule.md b/2021/info/faster-schedule.md index 1f092cb2..5057cdeb 100644 --- a/2021/info/faster-schedule.md +++ b/2021/info/faster-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Waiting for speaker to send prerecorded video +Duration: 20 minutes +Friendly URL: <a href="/2021/talks/faster">/2021/talks/faster</a> -Waiting for speaker to send prerecorded video +Sunday, Nov 28 2021, ~ 9:05 AM - 9:25 AM EST +Sunday, Nov 28 2021, ~ 6:05 AM - 6:25 AM PST +Sunday, Nov 28 2021, ~ 2:05 PM - 2:25 PM UTC +Sunday, Nov 28 2021, ~ 3:05 PM - 3:25 PM CET +Sunday, Nov 28 2021, ~10:05 PM - 10:25 PM +08 -# Schedule - -Allocated 20 minutes - - - -Friendly URL: <a href="/2021/talks/faster">/2021/talks/faster</a> +# Description diff --git a/2021/info/forever-schedule.md b/2021/info/forever-schedule.md index 00762619..2b61fac1 100644 --- a/2021/info/forever-schedule.md +++ b/2021/info/forever-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Waiting for speaker to send prerecorded video +Duration: 40 minutes +Friendly URL: <a href="/2021/talks/forever">/2021/talks/forever</a> -Waiting for speaker to send prerecorded video +Sunday, Nov 28 2021, ~ 4:03 PM - 4:43 PM EST +Sunday, Nov 28 2021, ~ 1:03 PM - 1:43 PM PST +Sunday, Nov 28 2021, ~ 9:03 PM - 9:43 PM UTC +Sunday, Nov 28 2021, ~10:03 PM - 10:43 PM CET +Monday, Nov 29 2021, ~ 5:03 AM - 5:43 AM +08 -# Schedule - -Allocated 40 minutes - - - -Friendly URL: <a href="/2021/talks/forever">/2021/talks/forever</a> +# Description diff --git a/2021/info/form-schedule.md b/2021/info/form-schedule.md index d8909b0b..d9a2883c 100644 --- a/2021/info/form-schedule.md +++ b/2021/info/form-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Waiting for speaker to send prerecorded video +Duration: 10 minutes +Friendly URL: <a href="/2021/talks/form">/2021/talks/form</a> -Waiting for speaker to send prerecorded video +Sunday, Nov 28 2021, ~ 1:27 PM - 1:37 PM EST +Sunday, Nov 28 2021, ~10:27 AM - 10:37 AM PST +Sunday, Nov 28 2021, ~ 6:27 PM - 6:37 PM UTC +Sunday, Nov 28 2021, ~ 7:27 PM - 7:37 PM CET +Monday, Nov 29 2021, ~ 2:27 AM - 2:37 AM +08 -# Schedule - -Allocated 10 minutes - - - -Friendly URL: <a href="/2021/talks/form">/2021/talks/form</a> +# Description diff --git a/2021/info/freedom-schedule.md b/2021/info/freedom-schedule.md index 1a7e78f7..4dc6097f 100644 --- a/2021/info/freedom-schedule.md +++ b/2021/info/freedom-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Captions added to video +Duration: 38 minutes +Friendly URL: <a href="/2021/talks/freedom">/2021/talks/freedom</a> -Captions added to video +Saturday, Nov 27 2021, ~ 4:20 PM - 4:58 PM EST +Saturday, Nov 27 2021, ~ 1:20 PM - 1:58 PM PST +Saturday, Nov 27 2021, ~ 9:20 PM - 9:58 PM UTC +Saturday, Nov 27 2021, ~10:20 PM - 10:58 PM CET +Sunday, Nov 28 2021, ~ 5:20 AM - 5:58 AM +08 -# Schedule - -Allocated 38 minutes - - - -Friendly URL: <a href="/2021/talks/freedom">/2021/talks/freedom</a> +# Description diff --git a/2021/info/frownies-schedule.md b/2021/info/frownies-schedule.md index 768fd6b5..e329a5b1 100644 --- a/2021/info/frownies-schedule.md +++ b/2021/info/frownies-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Captions added to video +Duration: 20 minutes +Friendly URL: <a href="/2021/talks/frownies">/2021/talks/frownies</a> -Captions added to video +Saturday, Nov 27 2021, ~ 9:11 AM - 9:31 AM EST +Saturday, Nov 27 2021, ~ 6:11 AM - 6:31 AM PST +Saturday, Nov 27 2021, ~ 2:11 PM - 2:31 PM UTC +Saturday, Nov 27 2021, ~ 3:11 PM - 3:31 PM CET +Saturday, Nov 27 2021, ~10:11 PM - 10:31 PM +08 -# Schedule - -Allocated 20 minutes - - - -Friendly URL: <a href="/2021/talks/frownies">/2021/talks/frownies</a> +# Description diff --git a/2021/info/gregorian-schedule.md b/2021/info/gregorian-schedule.md index 1fb2c491..43ff8ab9 100644 --- a/2021/info/gregorian-schedule.md +++ b/2021/info/gregorian-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Waiting for speaker to send prerecorded video +Duration: 10 minutes +Friendly URL: <a href="/2021/talks/gregorian">/2021/talks/gregorian</a> -Waiting for speaker to send prerecorded video +Saturday, Nov 27 2021, ~11:55 AM - 12:05 PM EST +Saturday, Nov 27 2021, ~ 8:55 AM - 9:05 AM PST +Saturday, Nov 27 2021, ~ 4:55 PM - 5:05 PM UTC +Saturday, Nov 27 2021, ~ 5:55 PM - 6:05 PM CET +Sunday, Nov 28 2021, ~12:55 AM - 1:05 AM +08 -# Schedule - -Allocated 10 minutes - - - -Friendly URL: <a href="/2021/talks/gregorian">/2021/talks/gregorian</a> +# Description diff --git a/2021/info/imaginary-schedule.md b/2021/info/imaginary-schedule.md index 549f4e81..213ec032 100644 --- a/2021/info/imaginary-schedule.md +++ b/2021/info/imaginary-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Prerecorded video received, waiting for captions +Duration: 11 minutes +Friendly URL: <a href="/2021/talks/imaginary">/2021/talks/imaginary</a> -Prerecorded video received, waiting for captions +Sunday, Nov 28 2021, ~ 3:22 PM - 3:33 PM EST +Sunday, Nov 28 2021, ~12:22 PM - 12:33 PM PST +Sunday, Nov 28 2021, ~ 8:22 PM - 8:33 PM UTC +Sunday, Nov 28 2021, ~ 9:22 PM - 9:33 PM CET +Monday, Nov 29 2021, ~ 4:22 AM - 4:33 AM +08 -# Schedule - -Allocated 11 minutes - - - -Friendly URL: <a href="/2021/talks/imaginary">/2021/talks/imaginary</a> +# Description diff --git a/2021/info/invoice-schedule.md b/2021/info/invoice-schedule.md index dab7eb15..1686f5f4 100644 --- a/2021/info/invoice-schedule.md +++ b/2021/info/invoice-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Captions added to video +Duration: 10 minutes +Friendly URL: <a href="/2021/talks/invoice">/2021/talks/invoice</a> -Captions added to video +Saturday, Nov 27 2021, ~ 3:16 PM - 3:26 PM EST +Saturday, Nov 27 2021, ~12:16 PM - 12:26 PM PST +Saturday, Nov 27 2021, ~ 8:16 PM - 8:26 PM UTC +Saturday, Nov 27 2021, ~ 9:16 PM - 9:26 PM CET +Sunday, Nov 28 2021, ~ 4:16 AM - 4:26 AM +08 -# Schedule - -Allocated 10 minutes - - - -Friendly URL: <a href="/2021/talks/invoice">/2021/talks/invoice</a> +# Description diff --git a/2021/info/janitor-schedule.md b/2021/info/janitor-schedule.md index 8fbc1f82..8fccc20b 100644 --- a/2021/info/janitor-schedule.md +++ b/2021/info/janitor-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Prerecorded video received, waiting for captions +Duration: 26 minutes +Friendly URL: <a href="/2021/talks/janitor">/2021/talks/janitor</a> -Prerecorded video received, waiting for captions +Saturday, Nov 27 2021, ~11:11 AM - 11:37 AM EST +Saturday, Nov 27 2021, ~ 8:11 AM - 8:37 AM PST +Saturday, Nov 27 2021, ~ 4:11 PM - 4:37 PM UTC +Saturday, Nov 27 2021, ~ 5:11 PM - 5:37 PM CET +Sunday, Nov 28 2021, ~12:11 AM - 12:37 AM +08 -# Schedule - -Allocated 26 minutes - - - -Friendly URL: <a href="/2021/talks/janitor">/2021/talks/janitor</a> +# Description diff --git a/2021/info/maintainers-schedule.md b/2021/info/maintainers-schedule.md index 8453ae55..38a5fa2f 100644 --- a/2021/info/maintainers-schedule.md +++ b/2021/info/maintainers-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Waiting for speaker to send prerecorded video +Duration: 10 minutes +Friendly URL: <a href="/2021/talks/maintainers">/2021/talks/maintainers</a> -Waiting for speaker to send prerecorded video +Saturday, Nov 27 2021, ~11:42 AM - 11:52 AM EST +Saturday, Nov 27 2021, ~ 8:42 AM - 8:52 AM PST +Saturday, Nov 27 2021, ~ 4:42 PM - 4:52 PM UTC +Saturday, Nov 27 2021, ~ 5:42 PM - 5:52 PM CET +Sunday, Nov 28 2021, ~12:42 AM - 12:52 AM +08 -# Schedule - -Allocated 10 minutes - - - -Friendly URL: <a href="/2021/talks/maintainers">/2021/talks/maintainers</a> +# Description diff --git a/2021/info/model-schedule.md b/2021/info/model-schedule.md index bdd631dc..55a86db3 100644 --- a/2021/info/model-schedule.md +++ b/2021/info/model-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Prerecorded video received, waiting for captions +Duration: 10 minutes +Friendly URL: <a href="/2021/talks/model">/2021/talks/model</a> -Prerecorded video received, waiting for captions +Sunday, Nov 28 2021, ~10:58 AM - 11:08 AM EST +Sunday, Nov 28 2021, ~ 7:58 AM - 8:08 AM PST +Sunday, Nov 28 2021, ~ 3:58 PM - 4:08 PM UTC +Sunday, Nov 28 2021, ~ 4:58 PM - 5:08 PM CET +Sunday, Nov 28 2021, ~11:58 PM - 12:08 AM +08 -# Schedule - -Allocated 10 minutes - - - -Friendly URL: <a href="/2021/talks/model">/2021/talks/model</a> +# Description diff --git a/2021/info/mold-schedule.md b/2021/info/mold-schedule.md index a01b5dbe..643e7fa8 100644 --- a/2021/info/mold-schedule.md +++ b/2021/info/mold-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Captions added to video +Duration: 10 minutes +Friendly URL: <a href="/2021/talks/mold">/2021/talks/mold</a> -Captions added to video +Sunday, Nov 28 2021, ~ 2:41 PM - 2:51 PM EST +Sunday, Nov 28 2021, ~11:41 AM - 11:51 AM PST +Sunday, Nov 28 2021, ~ 7:41 PM - 7:51 PM UTC +Sunday, Nov 28 2021, ~ 8:41 PM - 8:51 PM CET +Monday, Nov 29 2021, ~ 3:41 AM - 3:51 AM +08 -# Schedule - -Allocated 10 minutes - - - -Friendly URL: <a href="/2021/talks/mold">/2021/talks/mold</a> +# Description diff --git a/2021/info/molecular-schedule.md b/2021/info/molecular-schedule.md index 2c1b50a2..ee064c7d 100644 --- a/2021/info/molecular-schedule.md +++ b/2021/info/molecular-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Prerecorded video received, waiting for captions +Duration: 11 minutes +Friendly URL: <a href="/2021/talks/molecular">/2021/talks/molecular</a> -Prerecorded video received, waiting for captions +Saturday, Nov 27 2021, ~ 2:50 PM - 3:01 PM EST +Saturday, Nov 27 2021, ~11:50 AM - 12:01 PM PST +Saturday, Nov 27 2021, ~ 7:50 PM - 8:01 PM UTC +Saturday, Nov 27 2021, ~ 8:50 PM - 9:01 PM CET +Sunday, Nov 28 2021, ~ 3:50 AM - 4:01 AM +08 -# Schedule - -Allocated 11 minutes - - - -Friendly URL: <a href="/2021/talks/molecular">/2021/talks/molecular</a> +# Description diff --git a/2021/info/montessori-schedule.md b/2021/info/montessori-schedule.md index ddd8fdf9..b3ed453d 100644 --- a/2021/info/montessori-schedule.md +++ b/2021/info/montessori-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Waiting for speaker to send prerecorded video +Duration: 10 minutes +Friendly URL: <a href="/2021/talks/montessori">/2021/talks/montessori</a> -Waiting for speaker to send prerecorded video +Saturday, Nov 27 2021, ~12:30 PM - 12:40 PM EST +Saturday, Nov 27 2021, ~ 9:30 AM - 9:40 AM PST +Saturday, Nov 27 2021, ~ 5:30 PM - 5:40 PM UTC +Saturday, Nov 27 2021, ~ 6:30 PM - 6:40 PM CET +Sunday, Nov 28 2021, ~ 1:30 AM - 1:40 AM +08 -# Schedule - -Allocated 10 minutes - - - -Friendly URL: <a href="/2021/talks/montessori">/2021/talks/montessori</a> +# Description diff --git a/2021/info/nangulator-schedule.md b/2021/info/nangulator-schedule.md index ee64fae7..34a7087d 100644 --- a/2021/info/nangulator-schedule.md +++ b/2021/info/nangulator-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Waiting for speaker to send prerecorded video +Duration: 10 minutes +Friendly URL: <a href="/2021/talks/nangulator">/2021/talks/nangulator</a> -Waiting for speaker to send prerecorded video +Saturday, Nov 27 2021, ~10:58 AM - 11:08 AM EST +Saturday, Nov 27 2021, ~ 7:58 AM - 8:08 AM PST +Saturday, Nov 27 2021, ~ 3:58 PM - 4:08 PM UTC +Saturday, Nov 27 2021, ~ 4:58 PM - 5:08 PM CET +Saturday, Nov 27 2021, ~11:58 PM - 12:08 AM +08 -# Schedule - -Allocated 10 minutes - - - -Friendly URL: <a href="/2021/talks/nangulator">/2021/talks/nangulator</a> +# Description diff --git a/2021/info/native-schedule.md b/2021/info/native-schedule.md index 00e0666e..b56079f8 100644 --- a/2021/info/native-schedule.md +++ b/2021/info/native-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Waiting for speaker to send prerecorded video +Duration: 40 minutes +Friendly URL: <a href="/2021/talks/native">/2021/talks/native</a> -Waiting for speaker to send prerecorded video +Sunday, Nov 28 2021, ~12:40 PM - 1:20 PM EST +Sunday, Nov 28 2021, ~ 9:40 AM - 10:20 AM PST +Sunday, Nov 28 2021, ~ 5:40 PM - 6:20 PM UTC +Sunday, Nov 28 2021, ~ 6:40 PM - 7:20 PM CET +Monday, Nov 29 2021, ~ 1:40 AM - 2:20 AM +08 -# Schedule - -Allocated 40 minutes - - - -Friendly URL: <a href="/2021/talks/native">/2021/talks/native</a> +# Description diff --git a/2021/info/news-schedule.md b/2021/info/news-schedule.md index ce9cf23a..1337baa0 100644 --- a/2021/info/news-schedule.md +++ b/2021/info/news-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Captions added to video +Duration: 5 minutes +Friendly URL: <a href="/2021/talks/news">/2021/talks/news</a> -Captions added to video +Saturday, Nov 27 2021, ~ 9:05 AM - 9:10 AM EST +Saturday, Nov 27 2021, ~ 6:05 AM - 6:10 AM PST +Saturday, Nov 27 2021, ~ 2:05 PM - 2:10 PM UTC +Saturday, Nov 27 2021, ~ 3:05 PM - 3:10 PM CET +Saturday, Nov 27 2021, ~10:05 PM - 10:10 PM +08 -# Schedule - -Allocated 5 minutes - - - -Friendly URL: <a href="/2021/talks/news">/2021/talks/news</a> +# Description diff --git a/2021/info/nongnu-schedule.md b/2021/info/nongnu-schedule.md index 43e04a6e..ea6f99ab 100644 --- a/2021/info/nongnu-schedule.md +++ b/2021/info/nongnu-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Captions added to video +Duration: 7 minutes +Friendly URL: <a href="/2021/talks/nongnu">/2021/talks/nongnu</a> -Captions added to video +Saturday, Nov 27 2021, ~10:24 AM - 10:31 AM EST +Saturday, Nov 27 2021, ~ 7:24 AM - 7:31 AM PST +Saturday, Nov 27 2021, ~ 3:24 PM - 3:31 PM UTC +Saturday, Nov 27 2021, ~ 4:24 PM - 4:31 PM CET +Saturday, Nov 27 2021, ~11:24 PM - 11:31 PM +08 -# Schedule - -Allocated 7 minutes - - - -Friendly URL: <a href="/2021/talks/nongnu">/2021/talks/nongnu</a> +# Description diff --git a/2021/info/nyxt-schedule.md b/2021/info/nyxt-schedule.md index a7bea095..cb9cc450 100644 --- a/2021/info/nyxt-schedule.md +++ b/2021/info/nyxt-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Captions added to video +Duration: 10 minutes +Friendly URL: <a href="/2021/talks/nyxt">/2021/talks/nyxt</a> -Captions added to video +Saturday, Nov 27 2021, ~ 3:42 PM - 3:52 PM EST +Saturday, Nov 27 2021, ~12:42 PM - 12:52 PM PST +Saturday, Nov 27 2021, ~ 8:42 PM - 8:52 PM UTC +Saturday, Nov 27 2021, ~ 9:42 PM - 9:52 PM CET +Sunday, Nov 28 2021, ~ 4:42 AM - 4:52 AM +08 -# Schedule - -Allocated 10 minutes - - - -Friendly URL: <a href="/2021/talks/nyxt">/2021/talks/nyxt</a> +# Description diff --git a/2021/info/omegat-schedule.md b/2021/info/omegat-schedule.md index f11f1e24..ce8b81df 100644 --- a/2021/info/omegat-schedule.md +++ b/2021/info/omegat-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Prerecorded video received, waiting for captions +Duration: 10 minutes +Friendly URL: <a href="/2021/talks/omegat">/2021/talks/omegat</a> -Prerecorded video received, waiting for captions +Saturday, Nov 27 2021, ~10:11 AM - 10:21 AM EST +Saturday, Nov 27 2021, ~ 7:11 AM - 7:21 AM PST +Saturday, Nov 27 2021, ~ 3:11 PM - 3:21 PM UTC +Saturday, Nov 27 2021, ~ 4:11 PM - 4:21 PM CET +Saturday, Nov 27 2021, ~11:11 PM - 11:21 PM +08 -# Schedule - -Allocated 10 minutes - - - -Friendly URL: <a href="/2021/talks/omegat">/2021/talks/omegat</a> +# Description diff --git a/2021/info/org-outside-schedule.md b/2021/info/org-outside-schedule.md index e803a040..34547b75 100644 --- a/2021/info/org-outside-schedule.md +++ b/2021/info/org-outside-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Captions added to video +Duration: 12 minutes +Friendly URL: <a href="/2021/talks/org-outside">/2021/talks/org-outside</a> -Captions added to video +Saturday, Nov 27 2021, ~ 1:51 PM - 2:03 PM EST +Saturday, Nov 27 2021, ~10:51 AM - 11:03 AM PST +Saturday, Nov 27 2021, ~ 6:51 PM - 7:03 PM UTC +Saturday, Nov 27 2021, ~ 7:51 PM - 8:03 PM CET +Sunday, Nov 28 2021, ~ 2:51 AM - 3:03 AM +08 -# Schedule - -Allocated 12 minutes - - - -Friendly URL: <a href="/2021/talks/org-outside">/2021/talks/org-outside</a> +# Description diff --git a/2021/info/pattern-schedule.md b/2021/info/pattern-schedule.md index b573cdf1..86769317 100644 --- a/2021/info/pattern-schedule.md +++ b/2021/info/pattern-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Prerecorded video received, waiting for captions +Duration: 24 minutes +Friendly URL: <a href="/2021/talks/pattern">/2021/talks/pattern</a> -Prerecorded video received, waiting for captions +Saturday, Nov 27 2021, ~ 9:34 AM - 9:58 AM EST +Saturday, Nov 27 2021, ~ 6:34 AM - 6:58 AM PST +Saturday, Nov 27 2021, ~ 2:34 PM - 2:58 PM UTC +Saturday, Nov 27 2021, ~ 3:34 PM - 3:58 PM CET +Saturday, Nov 27 2021, ~10:34 PM - 10:58 PM +08 -# Schedule - -Allocated 24 minutes - - - -Friendly URL: <a href="/2021/talks/pattern">/2021/talks/pattern</a> +# Description diff --git a/2021/info/professional-schedule.md b/2021/info/professional-schedule.md index 3acc8521..63e94f5f 100644 --- a/2021/info/professional-schedule.md +++ b/2021/info/professional-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Captions added to video +Duration: 11 minutes +Friendly URL: <a href="/2021/talks/professional">/2021/talks/professional</a> -Captions added to video +Saturday, Nov 27 2021, ~ 1:14 PM - 1:25 PM EST +Saturday, Nov 27 2021, ~10:14 AM - 10:25 AM PST +Saturday, Nov 27 2021, ~ 6:14 PM - 6:25 PM UTC +Saturday, Nov 27 2021, ~ 7:14 PM - 7:25 PM CET +Sunday, Nov 28 2021, ~ 2:14 AM - 2:25 AM +08 -# Schedule - -Allocated 11 minutes - - - -Friendly URL: <a href="/2021/talks/professional">/2021/talks/professional</a> +# Description diff --git a/2021/info/project-schedule.md b/2021/info/project-schedule.md index 26e78b0b..04371d40 100644 --- a/2021/info/project-schedule.md +++ b/2021/info/project-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Waiting for speaker to send prerecorded video +Duration: 10 minutes +Friendly URL: <a href="/2021/talks/project">/2021/talks/project</a> -Waiting for speaker to send prerecorded video +Saturday, Nov 27 2021, ~ 3:03 PM - 3:13 PM EST +Saturday, Nov 27 2021, ~12:03 PM - 12:13 PM PST +Saturday, Nov 27 2021, ~ 8:03 PM - 8:13 PM UTC +Saturday, Nov 27 2021, ~ 9:03 PM - 9:13 PM CET +Sunday, Nov 28 2021, ~ 4:03 AM - 4:13 AM +08 -# Schedule - -Allocated 10 minutes - - - -Friendly URL: <a href="/2021/talks/project">/2021/talks/project</a> +# Description diff --git a/2021/info/research-schedule.md b/2021/info/research-schedule.md index e376ae83..e4e873b8 100644 --- a/2021/info/research-schedule.md +++ b/2021/info/research-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Waiting for speaker to send prerecorded video +Duration: 5 minutes +Friendly URL: <a href="/2021/talks/research">/2021/talks/research</a> -Waiting for speaker to send prerecorded video +Saturday, Nov 27 2021, ~ 2:29 PM - 2:34 PM EST +Saturday, Nov 27 2021, ~11:29 AM - 11:34 AM PST +Saturday, Nov 27 2021, ~ 7:29 PM - 7:34 PM UTC +Saturday, Nov 27 2021, ~ 8:29 PM - 8:34 PM CET +Sunday, Nov 28 2021, ~ 3:29 AM - 3:34 AM +08 -# Schedule - -Allocated 5 minutes - - - -Friendly URL: <a href="/2021/talks/research">/2021/talks/research</a> +# Description diff --git a/2021/info/rust-schedule.md b/2021/info/rust-schedule.md index 9a4cb61e..da7f8e17 100644 --- a/2021/info/rust-schedule.md +++ b/2021/info/rust-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Waiting for speaker to send prerecorded video +Duration: 20 minutes +Friendly URL: <a href="/2021/talks/rust">/2021/talks/rust</a> -Waiting for speaker to send prerecorded video +Sunday, Nov 28 2021, ~10:19 AM - 10:39 AM EST +Sunday, Nov 28 2021, ~ 7:19 AM - 7:39 AM PST +Sunday, Nov 28 2021, ~ 3:19 PM - 3:39 PM UTC +Sunday, Nov 28 2021, ~ 4:19 PM - 4:39 PM CET +Sunday, Nov 28 2021, ~11:19 PM - 11:39 PM +08 -# Schedule - -Allocated 20 minutes - - - -Friendly URL: <a href="/2021/talks/rust">/2021/talks/rust</a> +# Description diff --git a/2021/info/structural-schedule.md b/2021/info/structural-schedule.md index cc30d2a7..f88d14bd 100644 --- a/2021/info/structural-schedule.md +++ b/2021/info/structural-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Prerecorded video received, waiting for captions +Duration: 11 minutes +Friendly URL: <a href="/2021/talks/structural">/2021/talks/structural</a> -Prerecorded video received, waiting for captions +Sunday, Nov 28 2021, ~ 9:30 AM - 9:41 AM EST +Sunday, Nov 28 2021, ~ 6:30 AM - 6:41 AM PST +Sunday, Nov 28 2021, ~ 2:30 PM - 2:41 PM UTC +Sunday, Nov 28 2021, ~ 3:30 PM - 3:41 PM CET +Sunday, Nov 28 2021, ~10:30 PM - 10:41 PM +08 -# Schedule - -Allocated 11 minutes - - - -Friendly URL: <a href="/2021/talks/structural">/2021/talks/structural</a> +# Description diff --git a/2021/info/teach-schedule.md b/2021/info/teach-schedule.md index 562f7cf2..4cc6ec17 100644 --- a/2021/info/teach-schedule.md +++ b/2021/info/teach-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Prerecorded video received, waiting for captions +Duration: 21 minutes +Friendly URL: <a href="/2021/talks/teach">/2021/talks/teach</a> -Prerecorded video received, waiting for captions +Saturday, Nov 27 2021, ~ 2:04 PM - 2:25 PM EST +Saturday, Nov 27 2021, ~11:04 AM - 11:25 AM PST +Saturday, Nov 27 2021, ~ 7:04 PM - 7:25 PM UTC +Saturday, Nov 27 2021, ~ 8:04 PM - 8:25 PM CET +Sunday, Nov 28 2021, ~ 3:04 AM - 3:25 AM +08 -# Schedule - -Allocated 21 minutes - - - -Friendly URL: <a href="/2021/talks/teach">/2021/talks/teach</a> +# Description diff --git a/2021/info/tech-schedule.md b/2021/info/tech-schedule.md index cd6293da..e7de823c 100644 --- a/2021/info/tech-schedule.md +++ b/2021/info/tech-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Captions added to video +Duration: 11 minutes +Friendly URL: <a href="/2021/talks/tech">/2021/talks/tech</a> -Captions added to video +Saturday, Nov 27 2021, ~ 1:27 PM - 1:38 PM EST +Saturday, Nov 27 2021, ~10:27 AM - 10:38 AM PST +Saturday, Nov 27 2021, ~ 6:27 PM - 6:38 PM UTC +Saturday, Nov 27 2021, ~ 7:27 PM - 7:38 PM CET +Sunday, Nov 28 2021, ~ 2:27 AM - 2:38 AM +08 -# Schedule - -Allocated 11 minutes - - - -Friendly URL: <a href="/2021/talks/tech">/2021/talks/tech</a> +# Description diff --git a/2021/info/telega-schedule.md b/2021/info/telega-schedule.md index 50737950..c767a264 100644 --- a/2021/info/telega-schedule.md +++ b/2021/info/telega-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Captions added to video +Duration: 8 minutes +Friendly URL: <a href="/2021/talks/telega">/2021/talks/telega</a> -Captions added to video +Saturday, Nov 27 2021, ~10:48 AM - 10:56 AM EST +Saturday, Nov 27 2021, ~ 7:48 AM - 7:56 AM PST +Saturday, Nov 27 2021, ~ 3:48 PM - 3:56 PM UTC +Saturday, Nov 27 2021, ~ 4:48 PM - 4:56 PM CET +Saturday, Nov 27 2021, ~11:48 PM - 11:56 PM +08 -# Schedule - -Allocated 8 minutes - - - -Friendly URL: <a href="/2021/talks/telega">/2021/talks/telega</a> +# Description diff --git a/2021/info/test-schedule.md b/2021/info/test-schedule.md index a3cbe305..fd5382bf 100644 --- a/2021/info/test-schedule.md +++ b/2021/info/test-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Waiting for speaker to send prerecorded video +Duration: 5 minutes +Friendly URL: <a href="/2021/talks/test">/2021/talks/test</a> -Waiting for speaker to send prerecorded video +Sunday, Nov 28 2021, ~ 1:41 PM - 1:46 PM EST +Sunday, Nov 28 2021, ~10:41 AM - 10:46 AM PST +Sunday, Nov 28 2021, ~ 6:41 PM - 6:46 PM UTC +Sunday, Nov 28 2021, ~ 7:41 PM - 7:46 PM CET +Monday, Nov 29 2021, ~ 2:41 AM - 2:46 AM +08 -# Schedule - -Allocated 5 minutes - - - -Friendly URL: <a href="/2021/talks/test">/2021/talks/test</a> +# Description diff --git a/2021/info/ui-schedule.md b/2021/info/ui-schedule.md index 6a4999e6..0ca618ca 100644 --- a/2021/info/ui-schedule.md +++ b/2021/info/ui-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Waiting for speaker to send prerecorded video +Duration: 10 minutes +Friendly URL: <a href="/2021/talks/ui">/2021/talks/ui</a> -Waiting for speaker to send prerecorded video +Sunday, Nov 28 2021, ~10:06 AM - 10:16 AM EST +Sunday, Nov 28 2021, ~ 7:06 AM - 7:16 AM PST +Sunday, Nov 28 2021, ~ 3:06 PM - 3:16 PM UTC +Sunday, Nov 28 2021, ~ 4:06 PM - 4:16 PM CET +Sunday, Nov 28 2021, ~11:06 PM - 11:16 PM +08 -# Schedule - -Allocated 10 minutes - - - -Friendly URL: <a href="/2021/talks/ui">/2021/talks/ui</a> +# Description diff --git a/2021/info/unix-schedule.md b/2021/info/unix-schedule.md index 5cfcdc3c..71e29e7d 100644 --- a/2021/info/unix-schedule.md +++ b/2021/info/unix-schedule.md @@ -1,15 +1,15 @@ <!-- Automatically generated by conf-create-info-pages --> -# Status +Status: Captions added to video +Duration: 7 minutes +Friendly URL: <a href="/2021/talks/unix">/2021/talks/unix</a> -Captions added to video +Saturday, Nov 27 2021, ~10:00 AM - 10:07 AM EST +Saturday, Nov 27 2021, ~ 7:00 AM - 7:07 AM PST +Saturday, Nov 27 2021, ~ 3:00 PM - 3:07 PM UTC +Saturday, Nov 27 2021, ~ 4:00 PM - 4:07 PM CET +Saturday, Nov 27 2021, ~11:00 PM - 11:07 PM +08 -# Schedule - -Allocated 7 minutes - - - -Friendly URL: <a href="/2021/talks/unix">/2021/talks/unix</a> +# Description diff --git a/2021/schedule-details.md b/2021/schedule-details.md index 2c9ad075..77a755ad 100644 --- a/2021/schedule-details.md +++ b/2021/schedule-details.md @@ -1,59 +1,59 @@ -<table width="100%"><tr><td colspan="3"><strong>Saturday, Nov 27, 2021: General talks<strong></td></tr> -<tr><td colspan="3"><strong>Saturday morning<strong></td></tr> -<tr><td></td><td><a href="/2021/talks/day1-open">Opening remarks</a></td><td></td></tr> -<tr><td>captioned</td><td><a href="/2021/talks/news">Emacs News Highlights</a></td><td>Sacha Chua</td></tr> -<tr><td>captioned</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> -<tr><td>received</td><td><a href="/2021/talks/pattern">Emacs as Design Pattern Learning</a></td><td>Greta Goetz</td></tr> -<tr><td>captioned</td><td><a href="/2021/talks/unix">GNU's Not UNIX: Why Emacs Demonstrates The UNIX Philosophy Isn't Always The Only Answer</a></td><td>Daniel Rose</td></tr> -<tr><td>received</td><td><a href="/2021/talks/omegat">Emacs manuals translation and OmegaT</a></td><td>Jean-Christophe Helary</td></tr> -<tr><td>captioned</td><td><a href="/2021/talks/nongnu">NonGNU ELPA Update</a></td><td>Philip Kaludercic</td></tr> -<tr><td>captioned</td><td><a href="/2021/talks/borg">Manual Package Management in The Era of Repositories - Why and How</a></td><td>Dhavan (codingquark)</td></tr> -<tr><td>captioned</td><td><a href="/2021/talks/telega">telega.el and the Emacs community on Telegram</a></td><td>Gabriele Bozzola</td></tr> -<tr><td></td><td><a href="/2021/talks/nangulator">Introducing N-Angulator</a></td><td>Kevin Haddock</td></tr> -<tr><td>received</td><td><a href="/2021/talks/janitor">A day in the life of a janitor</a></td><td>Stefan Monnier</td></tr> -<tr><td></td><td><a href="/2021/talks/maintainers">How to help Emacs maintainers?</a></td><td>Bastien Guerry</td></tr> -<tr><td></td><td><a href="/2021/talks/gregorian">Typesetting Gregorian Chant with Emacs</a></td><td>Spencer King</td></tr> -<tr><td colspan="3"><strong>Saturday afternoon<strong></td></tr> -<tr><td></td><td><a href="/2021/talks/montessori">Emacs and Montessori Philosophy</a></td><td>Grant Shangreaux</td></tr> -<tr><td>captioned</td><td><a href="/2021/talks/erg">Emacs Research Group, Season Zero: What we did together with Emacs in 2 hours a week for a year</a></td><td>Noorah Alhasan, Joe Corneli, Raymond Puzio, Leo Vivier</td></tr> -<tr><td></td><td><a href="/2021/talks/cs">One effective CS grad student workflow</a></td><td>Greg Coladonato</td></tr> -<tr><td>captioned</td><td><a href="/2021/talks/professional">Using Org-Mode For Recording Continuous Professional Development</a></td><td>Philip Beadling</td></tr> -<tr><td>captioned</td><td><a href="/2021/talks/tech">Creating technical API documentation and presentations using org-babel, restclient, and org-treeslide</a></td><td>Jan Ypma</td></tr> -<tr><td>received</td><td><a href="/2021/talks/exec">Org as an executable format</a></td><td>Tom Gillespie</td></tr> -<tr><td>captioned</td><td><a href="/2021/talks/org-outside">The use of Org mode syntax outside of GNU/Emacs</a></td><td>Karl Voit</td></tr> -<tr><td>received</td><td><a href="/2021/talks/teach">Using Org-mode to teach programming</a></td><td>Daniel German</td></tr> -<tr><td></td><td><a href="/2021/talks/research">Managing a research workflow (bibliographies, note-taking, and arXiv)</a></td><td>Ahmed Khaled</td></tr> -<tr><td>received</td><td><a href="/2021/talks/babel">Babel for academics</a></td><td>Asilata Bapat</td></tr> -<tr><td>received</td><td><a href="/2021/talks/molecular">Reproducible molecular graphics with Org-mode</a></td><td>Blaine Mooers</td></tr> -<tr><td></td><td><a href="/2021/talks/project">Budgeting, Project Monitoring and Invoicing with Org Mode</a></td><td>Adolfo Villafiorita</td></tr> -<tr><td>captioned</td><td><a href="/2021/talks/invoice">Finding Your (In)voice: Emacs for Invoicing</a></td><td>Bala Ramadurai</td></tr> -<tr><td>captioned</td><td><a href="/2021/talks/dashboard">Productivity Dashboards with Emacs and Kindle</a></td><td>Mehmet Tekman</td></tr> -<tr><td>captioned</td><td><a href="/2021/talks/nyxt">Emacs with Nyxt: extend your editor with the power of a Lisp browser</a></td><td>Andrea</td></tr> -<tr><td>received</td><td><a href="/2021/talks/design">On the design of text editors</a></td><td>Nicolas P. Rougier</td></tr> -<tr><td>captioned</td><td><a href="/2021/talks/dev-update">Emacs development updates</a></td><td>John Wiegley</td></tr> -<tr><td>captioned</td><td><a href="/2021/talks/freedom">How Emacs made me appreciate software freedom</a></td><td>Protesilaos Stavrou</td></tr> -<tr><td></td><td><a href="/2021/talks/day1-close">Closing remarks day 1</a></td><td></td></tr> -<tr><td colspan="3"><strong>Sunday, Nov 28, 2021: Development talks<strong></td></tr> -<tr><td colspan="3"><strong>Sunday morning<strong></td></tr> -<tr><td></td><td><a href="/2021/talks/day2-open">Opening remarks day 2</a></td><td></td></tr> -<tr><td></td><td><a href="/2021/talks/faster">How to write faster Emacs Lisp</a></td><td>Dmitry Gutov</td></tr> -<tr><td>received</td><td><a href="/2021/talks/structural">Tree-edit: Structural editing for Java, Python, C, and beyond!</a></td><td>Ethan Leba</td></tr> -<tr><td></td><td><a href="/2021/talks/dsl">Self-Describing Smart DSL's: The Next Magits</a></td><td>Psionic</td></tr> -<tr><td></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><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><a href="/2021/talks/eaf">Emacs Application Framework: A 2021 Update</a></td><td>Matthew Zeng</td></tr> -<tr><td>received</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><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><a href="/2021/talks/bindat">Turbo Bindat</a></td><td>Stefan Monnier</td></tr> -<tr><td colspan="3"><strong>Sunday afternoon<strong></td></tr> -<tr><td></td><td><a href="/2021/talks/native">Emacs Lisp native compiler, current status and future developments</a></td><td>Andrea Corallo</td></tr> -<tr><td></td><td><a href="/2021/talks/form">Old McCarthy Had a Form</a></td><td>Ian Eure</td></tr> -<tr><td></td><td><a href="/2021/talks/test">Test blocks</a></td><td>Eduardo Ochs</td></tr> -<tr><td></td><td><a href="/2021/talks/bug">Let's talk about bug trackers</a></td><td>Bastien Guerry</td></tr> -<tr><td></td><td><a href="/2021/talks/bidi">Perso-Arabic Input Methods And Making More Emacs Apps BIDI Aware</a></td><td>Mohsen BANAN</td></tr> -<tr><td>captioned</td><td><a href="/2021/talks/mold">Moldable Emacs, a step towards sustainable software</a></td><td>Andrea</td></tr> -<tr><td></td><td><a href="/2021/talks/clede">CLEDE the Common Lisp Emacs Development Environment.</a></td><td>Fermin MF</td></tr> -<tr><td>received</td><td><a href="/2021/talks/imaginary">Imaginary Programming</a></td><td>Shane Mulligan</td></tr> -<tr><td></td><td><a href="/2021/talks/build">How to build an Emacs</a></td><td>Fermin MF</td></tr> -<tr><td></td><td><a href="/2021/talks/forever">M-x Forever: Why Emacs will outlast text editor trends</a></td><td>David Wilson (System Crafters)</td></tr> -<tr><td></td><td><a href="/2021/talks/day2-close">Closing remarks day 2</a></td><td></td></tr></table>
\ No newline at end of file +<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> +<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> +<tr><td>received</td><td width=100>~ 9:34 AM</td><td><a href="/2021/talks/pattern">Emacs as Design Pattern Learning</a></td><td>Greta Goetz</td></tr> +<tr><td>captioned</td><td width=100>~10:00 AM</td><td><a href="/2021/talks/unix">GNU's Not UNIX: Why Emacs Demonstrates The UNIX Philosophy Isn't Always The Only Answer</a></td><td>Daniel Rose</td></tr> +<tr><td>received</td><td width=100>~10:11 AM</td><td><a href="/2021/talks/omegat">Emacs manuals translation and OmegaT</a></td><td>Jean-Christophe Helary</td></tr> +<tr><td>captioned</td><td width=100>~10:24 AM</td><td><a href="/2021/talks/nongnu">NonGNU ELPA Update</a></td><td>Philip Kaludercic</td></tr> +<tr><td>captioned</td><td width=100>~10:36 AM</td><td><a href="/2021/talks/borg">Manual Package Management in The Era of Repositories - Why and How</a></td><td>Dhavan (codingquark)</td></tr> +<tr><td>captioned</td><td width=100>~10:48 AM</td><td><a href="/2021/talks/telega">telega.el and the Emacs community on Telegram</a></td><td>Gabriele Bozzola</td></tr> +<tr><td></td><td width=100>~10:58 AM</td><td><a href="/2021/talks/nangulator">Introducing N-Angulator</a></td><td>Kevin Haddock</td></tr> +<tr><td>received</td><td width=100>~11:11 AM</td><td><a href="/2021/talks/janitor">A day in the life of a janitor</a></td><td>Stefan Monnier</td></tr> +<tr><td></td><td width=100>~11:42 AM</td><td><a href="/2021/talks/maintainers">How to help Emacs maintainers?</a></td><td>Bastien Guerry</td></tr> +<tr><td></td><td width=100>~11:55 AM</td><td><a href="/2021/talks/gregorian">Typesetting Gregorian Chant with Emacs</a></td><td>Spencer King</td></tr> +<tr><td colspan="4"><strong>Saturday afternoon<strong></td></tr> +<tr><td></td><td width=100>~12:30 PM</td><td><a href="/2021/talks/montessori">Emacs and Montessori Philosophy</a></td><td>Grant Shangreaux</td></tr> +<tr><td>captioned</td><td width=100>~12:43 PM</td><td><a href="/2021/talks/erg">Emacs Research Group, Season Zero: What we did together with Emacs in 2 hours a week for a year</a></td><td>Noorah Alhasan, Joe Corneli, Raymond Puzio, Leo Vivier</td></tr> +<tr><td></td><td width=100>~ 1:01 PM</td><td><a href="/2021/talks/cs">One effective CS grad student workflow</a></td><td>Greg Coladonato</td></tr> +<tr><td>captioned</td><td width=100>~ 1:14 PM</td><td><a href="/2021/talks/professional">Using Org-Mode For Recording Continuous Professional Development</a></td><td>Philip Beadling</td></tr> +<tr><td>captioned</td><td width=100>~ 1:27 PM</td><td><a href="/2021/talks/tech">Creating technical API documentation and presentations using org-babel, restclient, and org-treeslide</a></td><td>Jan Ypma</td></tr> +<tr><td>received</td><td width=100>~ 1:40 PM</td><td><a href="/2021/talks/exec">Org as an executable format</a></td><td>Tom Gillespie</td></tr> +<tr><td>captioned</td><td width=100>~ 1:51 PM</td><td><a href="/2021/talks/org-outside">The use of Org mode syntax outside of GNU/Emacs</a></td><td>Karl Voit</td></tr> +<tr><td>received</td><td width=100>~ 2:04 PM</td><td><a href="/2021/talks/teach">Using Org-mode to teach programming</a></td><td>Daniel German</td></tr> +<tr><td></td><td width=100>~ 2:29 PM</td><td><a href="/2021/talks/research">Managing a research workflow (bibliographies, note-taking, and arXiv)</a></td><td>Ahmed Khaled</td></tr> +<tr><td>received</td><td width=100>~ 2:38 PM</td><td><a href="/2021/talks/babel">Babel for academics</a></td><td>Asilata Bapat</td></tr> +<tr><td>received</td><td width=100>~ 2:50 PM</td><td><a href="/2021/talks/molecular">Reproducible molecular graphics with Org-mode</a></td><td>Blaine Mooers</td></tr> +<tr><td></td><td width=100>~ 3:03 PM</td><td><a href="/2021/talks/project">Budgeting, Project Monitoring and Invoicing with Org Mode</a></td><td>Adolfo Villafiorita</td></tr> +<tr><td>captioned</td><td width=100>~ 3:16 PM</td><td><a href="/2021/talks/invoice">Finding Your (In)voice: Emacs for Invoicing</a></td><td>Bala Ramadurai</td></tr> +<tr><td>captioned</td><td width=100>~ 3:29 PM</td><td><a href="/2021/talks/dashboard">Productivity Dashboards with Emacs and Kindle</a></td><td>Mehmet Tekman</td></tr> +<tr><td>captioned</td><td width=100>~ 3:42 PM</td><td><a href="/2021/talks/nyxt">Emacs with Nyxt: extend your editor with the power of a Lisp browser</a></td><td>Andrea</td></tr> +<tr><td>received</td><td width=100>~ 3:55 PM</td><td><a href="/2021/talks/design">On the design of text editors</a></td><td>Nicolas P. Rougier</td></tr> +<tr><td>captioned</td><td width=100>~ 4:09 PM</td><td><a href="/2021/talks/dev-update">Emacs development updates</a></td><td>John Wiegley</td></tr> +<tr><td>captioned</td><td width=100>~ 4:20 PM</td><td><a href="/2021/talks/freedom">How Emacs made me appreciate software freedom</a></td><td>Protesilaos Stavrou</td></tr> +<tr><td></td><td width=100>~ 5:00 PM</td><td><a href="/2021/talks/day1-close">Closing remarks day 1</a></td><td></td></tr> +<tr><td colspan="4"><strong>Sunday, Nov 28, 2021: Development talks<strong></td></tr> +<tr><td colspan="4"><strong>Sunday morning<strong></td></tr> +<tr><td></td><td width=100>~ 9:00 AM</td><td><a href="/2021/talks/day2-open">Opening remarks day 2</a></td><td></td></tr> +<tr><td></td><td width=100>~ 9:05 AM</td><td><a href="/2021/talks/faster">How to write faster Emacs Lisp</a></td><td>Dmitry Gutov</td></tr> +<tr><td>received</td><td width=100>~ 9:30 AM</td><td><a href="/2021/talks/structural">Tree-edit: Structural editing for Java, Python, C, and beyond!</a></td><td>Ethan Leba</td></tr> +<tr><td></td><td width=100>~ 9:43 AM</td><td><a href="/2021/talks/dsl">Self-Describing Smart DSL's: The Next Magits</a></td><td>Psionic</td></tr> +<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></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> +<tr><td></td><td width=100>~12:40 PM</td><td><a href="/2021/talks/native">Emacs Lisp native compiler, current status and future developments</a></td><td>Andrea Corallo</td></tr> +<tr><td></td><td width=100>~ 1:27 PM</td><td><a href="/2021/talks/form">Old McCarthy Had a Form</a></td><td>Ian Eure</td></tr> +<tr><td></td><td width=100>~ 1:41 PM</td><td><a href="/2021/talks/test">Test blocks</a></td><td>Eduardo Ochs</td></tr> +<tr><td></td><td width=100>~ 1:49 PM</td><td><a href="/2021/talks/bug">Let's talk about bug trackers</a></td><td>Bastien Guerry</td></tr> +<tr><td></td><td width=100>~ 2:16 PM</td><td><a href="/2021/talks/bidi">Perso-Arabic Input Methods And Making More Emacs Apps BIDI Aware</a></td><td>Mohsen BANAN</td></tr> +<tr><td>captioned</td><td width=100>~ 2:41 PM</td><td><a href="/2021/talks/mold">Moldable Emacs, a step towards sustainable software</a></td><td>Andrea</td></tr> +<tr><td></td><td width=100>~ 2:55 PM</td><td><a href="/2021/talks/clede">CLEDE the Common Lisp Emacs Development Environment.</a></td><td>Fermin MF</td></tr> +<tr><td>received</td><td width=100>~ 3:22 PM</td><td><a href="/2021/talks/imaginary">Imaginary Programming</a></td><td>Shane Mulligan</td></tr> +<tr><td></td><td width=100>~ 3:36 PM</td><td><a href="/2021/talks/build">How to build an Emacs</a></td><td>Fermin MF</td></tr> +<tr><td></td><td width=100>~ 4:03 PM</td><td><a href="/2021/talks/forever">M-x Forever: Why Emacs will outlast text editor trends</a></td><td>David Wilson (System Crafters)</td></tr> +<tr><td></td><td width=100>~ 4:50 PM</td><td><a href="/2021/talks/day2-close">Closing remarks day 2</a></td><td></td></tr></table>
\ No newline at end of file diff --git a/2021/talks/babel.md b/2021/talks/babel.md index a42ba97d..53dda284 100644 --- a/2021/talks/babel.md +++ b/2021/talks/babel.md @@ -8,6 +8,8 @@ # Babel for academics Asilata Bapat +[[!inline pages="internal(2021/info/babel-schedule)" raw="yes"]] + 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 @@ -71,6 +73,4 @@ sessions, and tangling. --> -[[!inline pages="internal(2021/info/babel-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/babel-nav)" raw="yes"]] diff --git a/2021/talks/bidi.md b/2021/talks/bidi.md index 7bff4e8f..ae5f9027 100644 --- a/2021/talks/bidi.md +++ b/2021/talks/bidi.md @@ -8,6 +8,8 @@ # Perso-Arabic Input Methods And BIDI Aware Apps Mohsen BANAN -- محسن بنان +[[!inline pages="internal(2021/info/bidi-schedule)" raw="yes"]] + 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. @@ -101,6 +103,4 @@ References: <http://mohsen.1.banan.byname.net/persian> -- Farsi <http://mohsen.1.banan.byname.net/french> -- French -[[!inline pages="internal(2021/info/bidi-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/bidi-nav)" raw="yes"]] diff --git a/2021/talks/binary.md b/2021/talks/binary.md index 58689a55..215ea916 100644 --- a/2021/talks/binary.md +++ b/2021/talks/binary.md @@ -8,6 +8,8 @@ # Turbo Bindat Stefan Monnier +[[!inline pages="internal(2021/info/binary-schedule)" raw="yes"]] + 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 @@ -25,6 +27,4 @@ Bindat is an ELisp library to help manipulate binary data. -[[!inline pages="internal(2021/info/binary-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/binary-nav)" raw="yes"]] diff --git a/2021/talks/bindat.md b/2021/talks/bindat.md index c85616fc..d3d50b25 100644 --- a/2021/talks/bindat.md +++ b/2021/talks/bindat.md @@ -8,6 +8,8 @@ # Turbo Bindat Stefan Monnier +[[!inline pages="internal(2021/info/bindat-schedule)" raw="yes"]] + # Table of Contents @@ -29,6 +31,4 @@ show how we saved those. Not recommended for birds. -[[!inline pages="internal(2021/info/bindat-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/bindat-nav)" raw="yes"]] diff --git a/2021/talks/borg.md b/2021/talks/borg.md index 9a4b935a..8a90ba3b 100644 --- a/2021/talks/borg.md +++ b/2021/talks/borg.md @@ -8,6 +8,8 @@ # Manual Package Management in The Era of Repositories - Why and How Dhavan (codingquark) +[[!inline pages="internal(2021/info/borg-schedule)" raw="yes"]] + 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 @@ -28,6 +30,4 @@ Another Package and install all elisp code manually - with borg[1]. -[[!inline pages="internal(2021/info/borg-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/borg-nav)" raw="yes"]] diff --git a/2021/talks/bug.md b/2021/talks/bug.md index 6038d195..a9d33955 100644 --- a/2021/talks/bug.md +++ b/2021/talks/bug.md @@ -8,6 +8,8 @@ # Let's talk about bug trackers Bastien Guerry +[[!inline pages="internal(2021/info/bug-schedule)" raw="yes"]] + 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 @@ -17,6 +19,4 @@ tracker? -[[!inline pages="internal(2021/info/bug-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/bug-nav)" raw="yes"]] diff --git a/2021/talks/build.md b/2021/talks/build.md index 73f30450..83051434 100644 --- a/2021/talks/build.md +++ b/2021/talks/build.md @@ -8,6 +8,8 @@ # How to build an Emacs Fermin MF +[[!inline pages="internal(2021/info/build-schedule)" raw="yes"]] + 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 @@ -30,6 +32,4 @@ For more details about CEDAR: <https://gitlab.com/sasanidas/cedar> -[[!inline pages="internal(2021/info/build-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/build-nav)" raw="yes"]] diff --git a/2021/talks/clede.md b/2021/talks/clede.md index ded9bee4..97fe5dad 100644 --- a/2021/talks/clede.md +++ b/2021/talks/clede.md @@ -8,6 +8,8 @@ # CLEDE the Common Lisp Emacs Development Environment. Fermin MF +[[!inline pages="internal(2021/info/clede-schedule)" raw="yes"]] + 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 @@ -28,6 +30,4 @@ For more details: <https://gitlab.com/sasanidas/clede> -[[!inline pages="internal(2021/info/clede-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/clede-nav)" raw="yes"]] diff --git a/2021/talks/cs.md b/2021/talks/cs.md index a35dec9f..e6884e5a 100644 --- a/2021/talks/cs.md +++ b/2021/talks/cs.md @@ -8,6 +8,8 @@ # One effective CS grad student workflow Greg Coladonato +[[!inline pages="internal(2021/info/cs-schedule)" raw="yes"]] + 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 @@ -29,6 +31,4 @@ inspire others to build workflows that make them more productive. --> -[[!inline pages="internal(2021/info/cs-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/cs-nav)" raw="yes"]] diff --git a/2021/talks/dashboard.md b/2021/talks/dashboard.md index 8ceacc4b..cc244a98 100644 --- a/2021/talks/dashboard.md +++ b/2021/talks/dashboard.md @@ -8,6 +8,8 @@ # Productivity Dashboards with Emacs and Kindle Mehmet Tekman +[[!inline pages="internal(2021/info/dashboard-schedule)" raw="yes"]] + 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 @@ -146,6 +148,4 @@ easily managed from Emacs within a single Org-Mode file. --> -[[!inline pages="internal(2021/info/dashboard-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/dashboard-nav)" raw="yes"]] diff --git a/2021/talks/day1-close.md b/2021/talks/day1-close.md index 7707ba6a..deaffd84 100644 --- a/2021/talks/day1-close.md +++ b/2021/talks/day1-close.md @@ -8,8 +8,8 @@ # Closing remarks day 1 +[[!inline pages="internal(2021/info/day1-close-schedule)" raw="yes"]] -[[!inline pages="internal(2021/info/day1-close-schedule)" raw="yes"]] [[!inline pages="internal(2021/info/day1-close-nav)" raw="yes"]] diff --git a/2021/talks/day1-open.md b/2021/talks/day1-open.md index 70abc7c0..1ba7bfa0 100644 --- a/2021/talks/day1-open.md +++ b/2021/talks/day1-open.md @@ -8,8 +8,8 @@ # Opening remarks +[[!inline pages="internal(2021/info/day1-open-schedule)" raw="yes"]] -[[!inline pages="internal(2021/info/day1-open-schedule)" raw="yes"]] [[!inline pages="internal(2021/info/day1-open-nav)" raw="yes"]] diff --git a/2021/talks/day2-close.md b/2021/talks/day2-close.md index 721c9ae7..d66ea37b 100644 --- a/2021/talks/day2-close.md +++ b/2021/talks/day2-close.md @@ -8,8 +8,8 @@ # Closing remarks day 2 +[[!inline pages="internal(2021/info/day2-close-schedule)" raw="yes"]] -[[!inline pages="internal(2021/info/day2-close-schedule)" raw="yes"]] [[!inline pages="internal(2021/info/day2-close-nav)" raw="yes"]] diff --git a/2021/talks/day2-open.md b/2021/talks/day2-open.md index d6181726..336c0200 100644 --- a/2021/talks/day2-open.md +++ b/2021/talks/day2-open.md @@ -8,8 +8,8 @@ # Opening remarks day 2 +[[!inline pages="internal(2021/info/day2-open-schedule)" raw="yes"]] -[[!inline pages="internal(2021/info/day2-open-schedule)" raw="yes"]] [[!inline pages="internal(2021/info/day2-open-nav)" raw="yes"]] diff --git a/2021/talks/design.md b/2021/talks/design.md index 41c08c4c..a7144fbc 100644 --- a/2021/talks/design.md +++ b/2021/talks/design.md @@ -8,6 +8,8 @@ # On the design of text editors Nicolas P. Rougier +[[!inline pages="internal(2021/info/design-schedule)" raw="yes"]] + 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 @@ -38,6 +40,4 @@ alternatives using GNU Emacs. * Support my work at [github.com/sponsors/rougier](https://github.com/sponsors/rougier) or [en.liberapay.com/rougier/](https://en.liberapay.com/rougier/) -[[!inline pages="internal(2021/info/design-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/design-nav)" raw="yes"]] diff --git a/2021/talks/dev-update.md b/2021/talks/dev-update.md index 897aaa2d..18a103bf 100644 --- a/2021/talks/dev-update.md +++ b/2021/talks/dev-update.md @@ -8,8 +8,8 @@ # Emacs development updates John Wiegley +[[!inline pages="internal(2021/info/dev-update-schedule)" raw="yes"]] -[[!inline pages="internal(2021/info/dev-update-schedule)" raw="yes"]] [[!inline pages="internal(2021/info/dev-update-nav)" raw="yes"]] diff --git a/2021/talks/devel.md b/2021/talks/devel.md index 461f64f3..09009137 100644 --- a/2021/talks/devel.md +++ b/2021/talks/devel.md @@ -8,6 +8,8 @@ # Don't write that package! or: How I learned to stop worrying and love emacs-devel Stefan Kangas +[[!inline pages="internal(2021/info/devel-schedule)" raw="yes"]] + 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 @@ -33,6 +35,4 @@ 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! -[[!inline pages="internal(2021/info/devel-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/devel-nav)" raw="yes"]] diff --git a/2021/talks/dsl.md b/2021/talks/dsl.md index 9fb5cd47..e7b77e98 100644 --- a/2021/talks/dsl.md +++ b/2021/talks/dsl.md @@ -8,6 +8,8 @@ # Self-Describing Smart DSL's: The Next Magits Psionic +[[!inline pages="internal(2021/info/dsl-schedule)" raw="yes"]] + 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 @@ -43,6 +45,4 @@ self-describing modal programming system. -[[!inline pages="internal(2021/info/dsl-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/dsl-nav)" raw="yes"]] diff --git a/2021/talks/eaf.md b/2021/talks/eaf.md index 1bd64e5e..536aebaf 100644 --- a/2021/talks/eaf.md +++ b/2021/talks/eaf.md @@ -8,6 +8,8 @@ # Emacs Application Framework: A 2021 Update Matthew Zeng +[[!inline pages="internal(2021/info/eaf-schedule)" raw="yes"]] + 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 @@ -21,6 +23,4 @@ last year, this talk will briefly go over them. -[[!inline pages="internal(2021/info/eaf-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/eaf-nav)" raw="yes"]] diff --git a/2021/talks/erg.md b/2021/talks/erg.md index 72a70cff..c2c5e55e 100644 --- a/2021/talks/erg.md +++ b/2021/talks/erg.md @@ -8,6 +8,8 @@ # 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 +[[!inline pages="internal(2021/info/erg-schedule)" raw="yes"]] + 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 @@ -29,6 +31,4 @@ research communities similar to ours. -[[!inline pages="internal(2021/info/erg-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/erg-nav)" raw="yes"]] diff --git a/2021/talks/exec.md b/2021/talks/exec.md index e4d46aef..74df7fc7 100644 --- a/2021/talks/exec.md +++ b/2021/talks/exec.md @@ -8,6 +8,8 @@ # Org as an executable format Tom Gillespie +[[!inline pages="internal(2021/info/exec-schedule)" raw="yes"]] + Org mode is known for its flexibility, power, and staggeringly diverse number of workflows, users, and use cases. @@ -72,6 +74,4 @@ in incorporating such functionality into org-mode directly. --> -[[!inline pages="internal(2021/info/exec-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/exec-nav)" raw="yes"]] diff --git a/2021/talks/faster.md b/2021/talks/faster.md index 4e9b7752..6af1cf20 100644 --- a/2021/talks/faster.md +++ b/2021/talks/faster.md @@ -8,6 +8,8 @@ # How to write faster Emacs Lisp Dmitry Gutov +[[!inline pages="internal(2021/info/faster-schedule)" raw="yes"]] + - Before optimizing, benchmark first. - Different benchmarking approaches. - Live evaluation, step-debugging, measuring from a debugger breakpoint. @@ -19,6 +21,4 @@ Dmitry Gutov - Steps taken to speed up the Xref package recently. -[[!inline pages="internal(2021/info/faster-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/faster-nav)" raw="yes"]] diff --git a/2021/talks/forever.md b/2021/talks/forever.md index 0ba1c8b1..6f78ce92 100644 --- a/2021/talks/forever.md +++ b/2021/talks/forever.md @@ -8,6 +8,8 @@ # M-x Forever: Why Emacs will outlast text editor trends David Wilson +[[!inline pages="internal(2021/info/forever-schedule)" raw="yes"]] + 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 @@ -28,6 +30,4 @@ regardless of mainstream popularity. of popularity, and why (due to changing fashions, not usually better features). -[[!inline pages="internal(2021/info/forever-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/forever-nav)" raw="yes"]] diff --git a/2021/talks/form.md b/2021/talks/form.md index 12443a8f..7660e9ae 100644 --- a/2021/talks/form.md +++ b/2021/talks/form.md @@ -8,6 +8,8 @@ # Old McCarthy Had a Form Ian Eure +[[!inline pages="internal(2021/info/form-schedule)" raw="yes"]] + 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 @@ -53,6 +55,4 @@ modular, flexible Emacs Lisp. --> -[[!inline pages="internal(2021/info/form-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/form-nav)" raw="yes"]] diff --git a/2021/talks/freedom.md b/2021/talks/freedom.md index 09242583..5aef4bc3 100644 --- a/2021/talks/freedom.md +++ b/2021/talks/freedom.md @@ -8,6 +8,8 @@ # How Emacs made me appreciate software freedom Protesilaos Stavrou +[[!inline pages="internal(2021/info/freedom-schedule)" raw="yes"]] + 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 @@ -36,6 +38,4 @@ by it and thus reserve the right to modify it ahead of the main event. -[[!inline pages="internal(2021/info/freedom-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/freedom-nav)" raw="yes"]] diff --git a/2021/talks/frownies.md b/2021/talks/frownies.md index 9210309c..d9d1e0bc 100644 --- a/2021/talks/frownies.md +++ b/2021/talks/frownies.md @@ -8,6 +8,8 @@ # The True Frownies are the Friends We Made Along the Way: An Anecdote of Emacs's Malleability Case Duckworth +[[!inline pages="internal(2021/info/frownies-schedule)" raw="yes"]] + 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 @@ -36,6 +38,4 @@ teeth into. - [my Mastodon account](https://writing.exchange/@acdw) (though I'm moving to [tiny.tilde.website](https://tiny.tilde.website/@acdw) ... soon™) -[[!inline pages="internal(2021/info/frownies-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/frownies-nav)" raw="yes"]] diff --git a/2021/talks/gregorian.md b/2021/talks/gregorian.md index 1b1af064..094f3327 100644 --- a/2021/talks/gregorian.md +++ b/2021/talks/gregorian.md @@ -8,6 +8,8 @@ # Typesetting Gregorian Chant with Emacs Spencer King +[[!inline pages="internal(2021/info/gregorian-schedule)" raw="yes"]] + 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 @@ -31,6 +33,4 @@ own scores. -[[!inline pages="internal(2021/info/gregorian-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/gregorian-nav)" raw="yes"]] diff --git a/2021/talks/imaginary.md b/2021/talks/imaginary.md index 76bd46b9..bb299d0e 100644 --- a/2021/talks/imaginary.md +++ b/2021/talks/imaginary.md @@ -8,6 +8,8 @@ # Imaginary Programming Shane Mulligan +[[!inline pages="internal(2021/info/imaginary-schedule)" raw="yes"]] + 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 @@ -95,6 +97,4 @@ Shane Mulligan -[[!inline pages="internal(2021/info/imaginary-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/imaginary-nav)" raw="yes"]] diff --git a/2021/talks/invoice.md b/2021/talks/invoice.md index 74852c94..5acf1c88 100644 --- a/2021/talks/invoice.md +++ b/2021/talks/invoice.md @@ -8,6 +8,8 @@ # Find Your (In)voice: Emacs for Invoicing Bala Ramadurai +[[!inline pages="internal(2021/info/invoice-schedule)" raw="yes"]] + 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, @@ -37,6 +39,4 @@ We will use the following packages: -[[!inline pages="internal(2021/info/invoice-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/invoice-nav)" raw="yes"]] diff --git a/2021/talks/janitor.md b/2021/talks/janitor.md index 03063023..ae0eac57 100644 --- a/2021/talks/janitor.md +++ b/2021/talks/janitor.md @@ -8,6 +8,8 @@ # A day in the life of a janitor Stefan Monnier +[[!inline pages="internal(2021/info/janitor-schedule)" raw="yes"]] + 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 @@ -24,6 +26,4 @@ Because of a reckless former Emacs maintainer that shall -[[!inline pages="internal(2021/info/janitor-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/janitor-nav)" raw="yes"]] diff --git a/2021/talks/maintainers.md b/2021/talks/maintainers.md index 698090ee..80252750 100644 --- a/2021/talks/maintainers.md +++ b/2021/talks/maintainers.md @@ -8,6 +8,8 @@ # How to help Emacs maintainers? Bastien Guerry +[[!inline pages="internal(2021/info/maintainers-schedule)" raw="yes"]] + 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. @@ -20,6 +22,4 @@ care of Emacs maintainance by taking care of Emacs maintainers. -[[!inline pages="internal(2021/info/maintainers-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/maintainers-nav)" raw="yes"]] diff --git a/2021/talks/model.md b/2021/talks/model.md index edff5152..5928ece3 100644 --- a/2021/talks/model.md +++ b/2021/talks/model.md @@ -8,6 +8,8 @@ # Extending the "model" of Emacs to other applications Laszlo Krajnikovszkij +[[!inline pages="internal(2021/info/model-schedule)" raw="yes"]] + 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 @@ -98,6 +100,4 @@ productivity, computer literacy and the ideas of free software. --> -[[!inline pages="internal(2021/info/model-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/model-nav)" raw="yes"]] diff --git a/2021/talks/mold.md b/2021/talks/mold.md index 2135cc66..61273d78 100644 --- a/2021/talks/mold.md +++ b/2021/talks/mold.md @@ -8,6 +8,8 @@ # Moldable Emacs, a step towards sustainable software Andrea mailto:andrea-dev@hotmail.com - pronouns: he/him -- https://ag91.github.io +[[!inline pages="internal(2021/info/mold-schedule)" raw="yes"]] + 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. @@ -43,6 +45,4 @@ You can learn more about this at: <https://github.com/ag91/moldable-emacs> --> -[[!inline pages="internal(2021/info/mold-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/mold-nav)" raw="yes"]] diff --git a/2021/talks/molecular.md b/2021/talks/molecular.md index c319114a..f311e2b7 100644 --- a/2021/talks/molecular.md +++ b/2021/talks/molecular.md @@ -8,6 +8,8 @@ # Reproducible molecular graphics with Org-mode Blaine Mooers +[[!inline pages="internal(2021/info/molecular-schedule)" raw="yes"]] + 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 @@ -88,6 +90,4 @@ from Org-mode documents. --> -[[!inline pages="internal(2021/info/molecular-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/molecular-nav)" raw="yes"]] diff --git a/2021/talks/montessori.md b/2021/talks/montessori.md index abbf7a5c..43a5f5f2 100644 --- a/2021/talks/montessori.md +++ b/2021/talks/montessori.md @@ -8,6 +8,8 @@ # Emacs and Montessori Philosophy +[[!inline pages="internal(2021/info/montessori-schedule)" raw="yes"]] + 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 @@ -62,6 +64,4 @@ drives present in everybody that allow us to explore and make sense of our world --> -[[!inline pages="internal(2021/info/montessori-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/montessori-nav)" raw="yes"]] diff --git a/2021/talks/nangulator.md b/2021/talks/nangulator.md index 71ccdadd..ef20a655 100644 --- a/2021/talks/nangulator.md +++ b/2021/talks/nangulator.md @@ -8,6 +8,8 @@ # Introducing N-Angulator Kevin Haddock +[[!inline pages="internal(2021/info/nangulator-schedule)" raw="yes"]] + 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 @@ -58,6 +60,4 @@ Final questions/comments, contact info, and signing out. --> -[[!inline pages="internal(2021/info/nangulator-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/nangulator-nav)" raw="yes"]] diff --git a/2021/talks/native.md b/2021/talks/native.md index 700c1608..459fe66c 100644 --- a/2021/talks/native.md +++ b/2021/talks/native.md @@ -8,6 +8,8 @@ # Emacs Lisp native compiler, current status and future developments Andrea Corallo +[[!inline pages="internal(2021/info/native-schedule)" raw="yes"]] + 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 @@ -29,6 +31,4 @@ Format: 40 minutes -[[!inline pages="internal(2021/info/native-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/native-nav)" raw="yes"]] diff --git a/2021/talks/news.md b/2021/talks/news.md index db89f156..a69a0563 100644 --- a/2021/talks/news.md +++ b/2021/talks/news.md @@ -7,6 +7,8 @@ # Emacs News Highlights Sacha Chua <mailto:sacha@sachachua.com> - pronouns: she/her +[[!inline pages="internal(2021/info/news-schedule)" raw="yes"]] + Quick overview of Emacs community highlights since the last conference You can find the links and images at @@ -185,6 +187,4 @@ Posting the video early to help test formatting. [[!template text="That's all for this quick review." start="00:04:29.034" video="mainVideo" id=subtitle]] [[!template text="Enjoy the rest of EmacsConf 2021!" start="00:04:30.554" video="mainVideo" id=subtitle]] -[[!inline pages="internal(2021/info/news-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/news-nav)" raw="yes"]] diff --git a/2021/talks/nongnu.md b/2021/talks/nongnu.md index 00eb1a15..19303fc3 100644 --- a/2021/talks/nongnu.md +++ b/2021/talks/nongnu.md @@ -8,6 +8,8 @@ # NonGNU ELPA Update Philip Kaludercic +[[!inline pages="internal(2021/info/nongnu-schedule)" raw="yes"]] + 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 @@ -21,6 +23,4 @@ want their packages to be added to the repository. -[[!inline pages="internal(2021/info/nongnu-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/nongnu-nav)" raw="yes"]] diff --git a/2021/talks/nyxt.md b/2021/talks/nyxt.md index 62358903..ddd9331c 100644 --- a/2021/talks/nyxt.md +++ b/2021/talks/nyxt.md @@ -8,6 +8,8 @@ # 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 +[[!inline pages="internal(2021/info/nyxt-schedule)" raw="yes"]] + 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 @@ -34,6 +36,4 @@ You can learn more about this at: <https://github.com/ag91/emacs-with-nyxt> <!-- - 20 minutes: same as above plus some time to share Nyxt other capabilities and showing a workflow where you can go full circle: Emacs, Nyxt, Emacs --> -[[!inline pages="internal(2021/info/nyxt-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/nyxt-nav)" raw="yes"]] diff --git a/2021/talks/omegat.md b/2021/talks/omegat.md index 8fe9ec58..0ff72c14 100644 --- a/2021/talks/omegat.md +++ b/2021/talks/omegat.md @@ -8,6 +8,8 @@ # Emacs manuals translation and OmegaT Jean-Christophe Helary +[[!inline pages="internal(2021/info/omegat-schedule)" raw="yes"]] + 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. 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. @@ -60,6 +62,4 @@ People who are interested in knowing more about OmegaT are invited to check the - Links for sponsoring/supporting (multilingual translations): [https://doublet.jp](https://doublet.jp) -[[!inline pages="internal(2021/info/omegat-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/omegat-nav)" raw="yes"]] diff --git a/2021/talks/org-outside.md b/2021/talks/org-outside.md index 850601c9..be89af08 100644 --- a/2021/talks/org-outside.md +++ b/2021/talks/org-outside.md @@ -8,6 +8,8 @@ # The use of Org mode syntax outside of GNU/Emacs Karl Voit +[[!inline pages="internal(2021/info/org-outside-schedule)" raw="yes"]] + 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. @@ -42,6 +44,4 @@ or they have adapted Org mode in their workflows already. --> -[[!inline pages="internal(2021/info/org-outside-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/org-outside-nav)" raw="yes"]] diff --git a/2021/talks/pattern.md b/2021/talks/pattern.md index 688e2f56..e61677be 100644 --- a/2021/talks/pattern.md +++ b/2021/talks/pattern.md @@ -8,6 +8,8 @@ # Emacs as Design Pattern Learning Greta Goetz +[[!inline pages="internal(2021/info/pattern-schedule)" raw="yes"]] + 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). 1. Definition of design patterns and relation to Emacs @@ -80,6 +82,4 @@ fair use. -[[!inline pages="internal(2021/info/pattern-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/pattern-nav)" raw="yes"]] diff --git a/2021/talks/professional.md b/2021/talks/professional.md index 7223f33f..7ffa2a00 100644 --- a/2021/talks/professional.md +++ b/2021/talks/professional.md @@ -8,6 +8,8 @@ # Using Org-Mode For Recording Continuous Professional Development Philip Beadling +[[!inline pages="internal(2021/info/professional-schedule)" raw="yes"]] + 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 @@ -63,6 +65,4 @@ estimate this at approx 10 minutes. -[[!inline pages="internal(2021/info/professional-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/professional-nav)" raw="yes"]] diff --git a/2021/talks/project.md b/2021/talks/project.md index b21fa546..acb6696f 100644 --- a/2021/talks/project.md +++ b/2021/talks/project.md @@ -8,6 +8,8 @@ # Budgeting, Project Monitoring and Invoicing with Org Mode Adolfo Villafiorita +[[!inline pages="internal(2021/info/project-schedule)" raw="yes"]] + In this talk I will present how we use Org Mode at Shair.Tech for budgeting, project monitoring, and invoicing. @@ -23,6 +25,4 @@ year, now, and with which we are very happy. Talk duration: -[[!inline pages="internal(2021/info/project-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/project-nav)" raw="yes"]] diff --git a/2021/talks/research.md b/2021/talks/research.md index c6f2e200..3a3cbc29 100644 --- a/2021/talks/research.md +++ b/2021/talks/research.md @@ -8,6 +8,8 @@ # Managing a research workflow (bibliographies, note-taking, and arXiv) Ahmed Khaled +[[!inline pages="internal(2021/info/research-schedule)" raw="yes"]] + 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 @@ -43,6 +45,4 @@ include a video segment on configuring the packages in Emacs. --> -[[!inline pages="internal(2021/info/research-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/research-nav)" raw="yes"]] diff --git a/2021/talks/rust.md b/2021/talks/rust.md index 9ebab731..c87ce1f6 100644 --- a/2021/talks/rust.md +++ b/2021/talks/rust.md @@ -8,6 +8,8 @@ # Extending Emacs in Rust with Dynamic Modules Tuấn-Anh Nguyễn +[[!inline pages="internal(2021/info/rust-schedule)" raw="yes"]] + 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 @@ -30,6 +32,4 @@ dynamic modules in Rust. -[[!inline pages="internal(2021/info/rust-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/rust-nav)" raw="yes"]] diff --git a/2021/talks/structural.md b/2021/talks/structural.md index d1fca711..b35ca438 100644 --- a/2021/talks/structural.md +++ b/2021/talks/structural.md @@ -8,6 +8,8 @@ # Tree-edit: Structural editing for Java, Python, C, and beyond! Ethan Leba +[[!inline pages="internal(2021/info/structural-schedule)" raw="yes"]] + 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 @@ -52,6 +54,4 @@ same as 20 minutes, with more detailed discussion of the implementation. --> -[[!inline pages="internal(2021/info/structural-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/structural-nav)" raw="yes"]] diff --git a/2021/talks/teach.md b/2021/talks/teach.md index 03d82734..761e7fd3 100644 --- a/2021/talks/teach.md +++ b/2021/talks/teach.md @@ -8,6 +8,8 @@ # Using Org-mode to teach programming Daniel German +[[!inline pages="internal(2021/info/teach-schedule)" raw="yes"]] + In this presentation I will explain how to use org-mode effectively to prepare teaching materials, and how to present them. @@ -46,6 +48,4 @@ I have create a git repository with examples and config files that is ready to u -[[!inline pages="internal(2021/info/teach-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/teach-nav)" raw="yes"]] diff --git a/2021/talks/tech.md b/2021/talks/tech.md index d091d132..d090ecfe 100644 --- a/2021/talks/tech.md +++ b/2021/talks/tech.md @@ -8,6 +8,8 @@ # Creating technical API documentation and presentations using org-babel, restclient, and org-treeslide Jan Ypma +[[!inline pages="internal(2021/info/tech-schedule)" raw="yes"]] + 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 @@ -31,6 +33,4 @@ org-treeslide to write and present technical documentation with style. - Demo: Presentations - Used packages and configuration -[[!inline pages="internal(2021/info/tech-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/tech-nav)" raw="yes"]] diff --git a/2021/talks/telega.md b/2021/talks/telega.md index f89d416e..810b4023 100644 --- a/2021/talks/telega.md +++ b/2021/talks/telega.md @@ -8,6 +8,8 @@ # telega.el and the Emacs community on Telegram Gabriele Bozzola and Evgeny Zajcev +[[!inline pages="internal(2021/info/telega-schedule)" raw="yes"]] + 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 @@ -20,6 +22,4 @@ highlight some of the most important features. -[[!inline pages="internal(2021/info/telega-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/telega-nav)" raw="yes"]] diff --git a/2021/talks/test.md b/2021/talks/test.md index 06286b7c..84ec5ea1 100644 --- a/2021/talks/test.md +++ b/2021/talks/test.md @@ -8,6 +8,8 @@ # Test blocks Eduardo Ochs +[[!inline pages="internal(2021/info/test-schedule)" raw="yes"]] + 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. @@ -42,6 +44,4 @@ Eduardo Ochs <http://angg.twu.net/emacsconf2021.html> -[[!inline pages="internal(2021/info/test-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/test-nav)" raw="yes"]] diff --git a/2021/talks/ui.md b/2021/talks/ui.md index 01ed2b26..50f5c992 100644 --- a/2021/talks/ui.md +++ b/2021/talks/ui.md @@ -8,6 +8,8 @@ # "Yak-shaving to a UI framework" (/"Help! I accidentally yak-shaved my way to writing a UI framework because overlays were slow") Erik Anderson +[[!inline pages="internal(2021/info/ui-schedule)" raw="yes"]] + 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 @@ -39,6 +41,4 @@ by implementing some basic UI's. ---> -[[!inline pages="internal(2021/info/ui-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/ui-nav)" raw="yes"]] diff --git a/2021/talks/unix.md b/2021/talks/unix.md index 947730b1..fce37364 100644 --- a/2021/talks/unix.md +++ b/2021/talks/unix.md @@ -8,6 +8,8 @@ # GNU's Not UNIX: Why Emacs Demonstrates The UNIX Philosophy Isn't Always The Only Answer Daniel Rose +[[!inline pages="internal(2021/info/unix-schedule)" raw="yes"]] + 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 @@ -45,6 +47,4 @@ to be more performant than without. --> -[[!inline pages="internal(2021/info/unix-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/unix-nav)" raw="yes"]] diff --git a/2021/talks/world.md b/2021/talks/world.md index 86c30653..007e4a3f 100644 --- a/2021/talks/world.md +++ b/2021/talks/world.md @@ -8,6 +8,8 @@ # World Citizen Mohsen BANAN +[[!inline pages="internal(2021/info/world-schedule)" raw="yes"]] + Starting with Emacs 24, full native bidi (bidirectional) support became available. For many years prior to that Unicode support was @@ -68,6 +70,4 @@ environment that can be. -[[!inline pages="internal(2021/info/world-schedule)" raw="yes"]] - [[!inline pages="internal(2021/info/world-nav)" raw="yes"]] |