diff options
Diffstat (limited to '2025/talks')
| -rw-r--r-- | 2025/talks/blee-lcnt.md | 109 | ||||
| -rw-r--r-- | 2025/talks/bookclub-tapas.md | 73 | ||||
| -rw-r--r-- | 2025/talks/calc.md | 26 | ||||
| -rw-r--r-- | 2025/talks/greader.md | 3 | ||||
| -rw-r--r-- | 2025/talks/modern.md | 35 | ||||
| -rw-r--r-- | 2025/talks/private-ai.md | 32 | ||||
| -rw-r--r-- | 2025/talks/schemacs.md | 90 | ||||
| -rw-r--r-- | 2025/talks/weights.md | 41 | ||||
| -rw-r--r-- | 2025/talks/zettelkasten.md | 47 |
9 files changed, 455 insertions, 1 deletions
diff --git a/2025/talks/blee-lcnt.md b/2025/talks/blee-lcnt.md new file mode 100644 index 00000000..285c6680 --- /dev/null +++ b/2025/talks/blee-lcnt.md @@ -0,0 +1,109 @@ +[[!meta title="Blee-LCNT: An Emacs-centered content production and self-publication framework"]] +[[!meta copyright="Copyright © 2025 Mohsen BANAN"]] +[[!inline pages="internal(2025/info/blee-lcnt-nav)" raw="yes"]] + +<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing --> +<!-- You can manually edit this file to update the abstract, add links, etc. ---> + + +# Blee-LCNT: An Emacs-centered content production and self-publication framework +Mohsen BANAN (he/him) - Pronunciation: MO-HH-SS-EN, <http://mohsen.1.banan.byname.net> + +[[!inline pages="internal(2025/info/blee-lcnt-before)" raw="yes"]] + +In a sense this is yet another talk about how you +can use Emacs to produce fancy presentations like +this or write complex books and self-publish them. +But our approach is fundamentally different. + +Many talks at previous Emacs Conferences have +described how Emacs and org-mode can be extended +to facilitate content production by adding more to +Emacs. Our approach is that of putting a smaller +Emacs at the core of something bigger. That +something bigger is an autonomy oriented digital +ecosystem called "ByStar" which is uniformly built +with a layer on top of Debian called BISOS (ByStar +Internet Services OS). + +At Emacs Conf-2024 the title of my talk was "About Blee" – +<https://emacsconf.org/2024/talks/blee>. +Blee (ByStar Libre-Halaal Emacs Environment) is that +smaller Emacs packaging that positions Emacs at the core of BISOS and +ByStar. BISOS and Blee are intertwined and +ByStar is about autonomy oriented unified platforms for developing and +delivering both internet services and +software-service continuums. + +This talk is about Content Production and Self-Publication capabilities of +Blee and BISOS. + +Blee-LCNT is LaTeX centric. The original text is always in COMEEGA-LaTeX – +LaTeX augmented by Org-Mode. This is +the inverse direction of exporting LaTeX from Org-Mode. For typesetting, +the LaTeX syntax is far more powerful than +org-mode. And with COMEEGA-LaTeX, you can also benefit from all that +org-mode offers. The scope of Blee-LCNT is all +types of content from presentations to videos to books to name-tags and +business cards. + +LaTeX to HTML translation is done with HeVeA. For +presentation/screen-casting, the original text is then augmented +in layers by images, audio voice-overs, screen captures, videos and +captions. The Beamer LaTeX file is then +processed by both LaTeX and HeVeA. LaTeX produced slides are then absorbed +in html by HeVeA as images. HeVeA output +is destined to be dispensed by Reveal.js. The video is then just a screen +capture of the autoplay of reveal file. +Viewing presentations in their original Reveal form makes for an even +richer experience. + +All of this involves a whole lot of integration and scripting. But all of +that has been done and you can get it all +in one shot by just running one script. + +To get started with BISOS, Blee, and ByStar, visit +<https://github.com/bxgenesis/start>. From a vanilla Debian 13 +installation ("Fresh-Debian"), you can bootstrap BISOS and Blee (with +Emacs-30) in one step by running the +raw-bisos.sh script. It produces "Raw-BISOS" which includes "Raw-Blee". + +You can then add the LaTeX sources for your content as ByStar Portable +Objects (BPO) to BISOS and process +your content with Blee-LCNT. + +All of this and more has been documented in a book that was produced by +Blee-LCNT itself. +The title of that book is: + +Nature of Polyexistentials: +Basis for Abolishment of the Western Intellectual Property Rights Regime +And Introduction of the Libre-Halaal ByStar Digital Ecosystem + +- On Line US Edition: <https://github.com/bxplpc/120033> – Download: + +<https://raw.github.com/bxplpc/120033/main/pdf/c-120033-1_05-book-8.5x11-col-emb-pub.pdf> + +- On Line International Edition: <https://github.com/bxplpc/120074> – + +Download: +<https://raw.github.com/bxplpc/120074/main/pdf/c-120074-1_05-book-a4-col-emb-pub.pdf> +DOI: <https://doi.org/10.5281/zenodo.8003846> + +- US Edition Book Prints At Amazon: <https://www.amazon.com/dp/1960957015> +- International Edition Book Prints in Iran: + +<https://jangal.com/fa/product/252689/nature-of-polyexistentials> + +I welcome your thoughts and feedback, especially if you experiment with +Blee, +BISOS, ByStar, and the model and the concept of Libre-Halaal +Polyexistentials. + + + +[[!inline pages="internal(2025/info/blee-lcnt-after)" raw="yes"]] + +[[!inline pages="internal(2025/info/blee-lcnt-nav)" raw="yes"]] + + diff --git a/2025/talks/bookclub-tapas.md b/2025/talks/bookclub-tapas.md new file mode 100644 index 00000000..5d0574b1 --- /dev/null +++ b/2025/talks/bookclub-tapas.md @@ -0,0 +1,73 @@ +[[!meta title="Bookclub tapas"]] +[[!meta copyright="Copyright © 2025 Maddie Sullivan"]] +[[!inline pages="internal(2025/info/bookclub-tapas-nav)" raw="yes"]] + +<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing --> +<!-- You can manually edit this file to update the abstract, add links, etc. ---> + + +# Bookclub tapas +Maddie Sullivan (she/her) - IRC: ElephantErgo, <https://ElephantErgonomics.com>, <mailto:hello@ElephantErgonomics.com> + +[[!inline pages="internal(2025/info/bookclub-tapas-before)" raw="yes"]] + +I've been experimenting with a new programming methodology that I've +stumbled upon. I call it "Bookclub Tapas". It is comprised of two parts, +"Bookclub" and "Tapas". Together, they form a literate-inspired, +Agile-inspired development method which centers around developer +self-reflection as a means to chip away at identifying powerful custom-fit +abstractions. + +Bookclub turns literate programming on its head by having the target +audience of the source document's commentary be its own developer. Bookclub +files contain source code, issue tracking, research, feature requests, and +reflections on the development process all seamlessly integrated into a +single file. Developers no longer have to worry about keeping track of what +they want to be doing, why they want to do something, or even the full +picture of how to go about doing something, because the Bookclub file acts +in cooperative conversation with the developer as a living record of their +hopes, intentions, and efforts. + +Tapas is the idea that instead of writing stand-alone programs, we write +library ecosystems. Instead of getting ahead of ourselves by trying +immediately to write large programs to solve large problems, we instead +focus on writing abstractions that reduce the scale of our problem. Our +goal is to identify what sort of tool would make the problem at hand +trivial to solve, implement said tool, and even work recursively to +implement tools to implement our tools. Our goal is that each next level of +abstraction is roughly a three-line trivial case of the level of +abstraction below, and eventually the solution to our initial problem is +itself trivial. + +Over the course of the talk, I intend to dive into what is Bookclub, what +is Tapas, what do they look like when used together, and why they provide a +meaningful set of methodologies both for getting real work done and also +elevating the programming process' beauty. I will use a live demo centered +around light development on a real-life yet-to-be-released Emacs Lisp +package. I intend to showcase how Org Babel enables Bookclub by allowing +for incredibly malleable documents that seamlessly integrate source code, +documentation, issue tracking, research, and even the build process. I also +intend to showcase how the Emacs Lisp macro system enables Tapas by +allowing us to recontextualize and reinvent syntax in order to build +powerful, composable abstractions that do exactly what the context calls +for while using phrasing that is both natural and intuitive. + +About the speaker: + +Hi! I'm Maddie Sullivan, my pronouns are she/her, my handle is +ElephantErgonomics (ElephantErgo on IRC), and my email is +hello@ElephantErgonomics.com. My talk is on a programming methodology I've +stumbled into that I've come to call "Bookclub Tapas". It's inspired by +literate, agile, and last year's Emacsconf! I've had great success with it +for my personal development process, and I'm hoping you can get something +out of it as well. I'll be laying out what it is, how I found it, why Emacs +makes an awesome environment for it, and how you can get started with it +too! + + + +[[!inline pages="internal(2025/info/bookclub-tapas-after)" raw="yes"]] + +[[!inline pages="internal(2025/info/bookclub-tapas-nav)" raw="yes"]] + + diff --git a/2025/talks/calc.md b/2025/talks/calc.md new file mode 100644 index 00000000..b0172603 --- /dev/null +++ b/2025/talks/calc.md @@ -0,0 +1,26 @@ +[[!meta title="Basic Calc functionality for engineering or electronics"]] +[[!meta copyright="Copyright © 2025 Christopher Howard"]] +[[!inline pages="internal(2025/info/calc-nav)" raw="yes"]] + +<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing --> +<!-- You can manually edit this file to update the abstract, add links, etc. ---> + + +# Basic Calc functionality for engineering or electronics +Christopher Howard (he/him) - IRC: lispmacs or lispmacs[work], gemini capsule: gemini://gem.librehacker.com, <mailto:christopher@librehacker.com> + +[[!inline pages="internal(2025/info/calc-before)" raw="yes"]] + +An introduction to some of the basic Algebra and Calculus functionality in Calc, as might be useful in engineering or electronics. + +About the speaker: + +Christopher Howard is a simulator technician in Fairbanks, Alaska, and a GNU Emacs user for a little over a decade. My technical interests are focused on analog computing and modeling with differential equations. + + + +[[!inline pages="internal(2025/info/calc-after)" raw="yes"]] + +[[!inline pages="internal(2025/info/calc-nav)" raw="yes"]] + + diff --git a/2025/talks/greader.md b/2025/talks/greader.md index e488b57d..4ea18f74 100644 --- a/2025/talks/greader.md +++ b/2025/talks/greader.md @@ -7,7 +7,8 @@ # GNU Emacs Greader (Gnamù Reader) mode is the best Emacs mode in existence -Yuval Langer (he/him) - Pronunciation: /juval/ /lˈangeʁ/, IRC: cow_2001, <https://kaka.farm/>, @kakafarm@shitposter.world, <mailto:yuval.langer@gmail.com> +Yuval Langer (he/him) - Pronunciation: /juval/ /lˈangeʁ/, IRC: cow_2001, <https://kaka.farm/>, +@kakafarm@shitposter.world, <mailto:yuval.langer@gmail.com> [[!inline pages="internal(2025/info/greader-before)" raw="yes"]] diff --git a/2025/talks/modern.md b/2025/talks/modern.md new file mode 100644 index 00000000..5d60bcc1 --- /dev/null +++ b/2025/talks/modern.md @@ -0,0 +1,35 @@ +[[!meta title="Some problems of modernizing Emacs"]] +[[!meta copyright="Copyright © 2025 Eduardo Ochs"]] +[[!inline pages="internal(2025/info/modern-nav)" raw="yes"]] + +<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing --> +<!-- You can manually edit this file to update the abstract, add links, etc. ---> + + +# Some problems of modernizing Emacs +Eduardo Ochs (he/him) - Pronunciation: Oks, IRC: edrx, <http://anggtwu.net/>, more info at <http://anggtwu.net/contact.html>., <mailto:eduardoochs@gmail.com> + +[[!inline pages="internal(2025/info/modern-before)" raw="yes"]] + +This talk is going to be a reworked version of the incomplete video +in <http://anggtwu.net/2025-modern.html>. I will start by presenting +several notions of "simplicity" and "elegance", and show that when I +started learning Elisp it was "simple" and "elegant" in a way that +it no longer is; then I will show how to fix some tiny parts of the +problem by 1) using functions based on \`cl-prin1', 2) redefining +some printing methods with "(cl-defmethod cl-print-object …)", and 3) using Common Lisp to understand some recent parts of Elisp that are not well-documented. + +About the speaker: + +Eduardo is the author of an Emacs package called eev that makes +total sense to a handful of people and no sense at all to +practically everyone else - except for one part of eev, called +"eepitch". He intends to explain the reasons for that in his talk. + + + +[[!inline pages="internal(2025/info/modern-after)" raw="yes"]] + +[[!inline pages="internal(2025/info/modern-nav)" raw="yes"]] + + diff --git a/2025/talks/private-ai.md b/2025/talks/private-ai.md new file mode 100644 index 00000000..55660ac2 --- /dev/null +++ b/2025/talks/private-ai.md @@ -0,0 +1,32 @@ +[[!meta title="Emacs and private AI: a great match"]] +[[!meta copyright="Copyright © 2025 Aaron Grothe"]] +[[!inline pages="internal(2025/info/private-ai-nav)" raw="yes"]] + +<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing --> +<!-- You can manually edit this file to update the abstract, add links, etc. ---> + + +# Emacs and private AI: a great match +Aaron Grothe (he/him) - Pronunciation: Air-un Grow-the, <https://www.grothe.us> LinkedIn: <https://www.linkedin.com/in/aaron-grothe/>, <mailto:ajgrothe@yahoo.com> + +[[!inline pages="internal(2025/info/private-ai-before)" raw="yes"]] + +When experimenting with using AI with Emacs, many users have concerns. A few of the concerns that people have are the possibility of their information being shared with the AI provider (either to train newer models, or as a potential revenue source), the possibility of running up unpredictable costs with their cloud provider, and the potential environmental impact of using cloud AI. Using Private/Local AI models provide an AI environment that the user can fully control. User can add to it incrementally over time as their skills and experience grows. This talk will be a quick intro to using Ollama Buddy, Ellama, and gptel to add the ability to have a private AI integrated into your Emacs session. We’ll start with the basics and show people how they can add AI to their workflow safely and securely. Hopefully, people will come away from the talk feeling better about our AI futures. + +The talk will start with a simple implementation: Ollama and Ollama Buddy and a couple of models. After that it will build on that +for the rest of the 20 minutes. + +The goal is show the users multiple ways of using AI with Emacs and let them make their own choices. + +About the speaker: + +AI is everywhere and everyone is trying to figure out how to use it better. This talk will be a quick introduction to showing some +of the tools and techniques that a user can do to integrate AI privately and securely into their Emacs workflow. The goal is to help people take the first steps on what will hopefully be a productive journey. + + + +[[!inline pages="internal(2025/info/private-ai-after)" raw="yes"]] + +[[!inline pages="internal(2025/info/private-ai-nav)" raw="yes"]] + + diff --git a/2025/talks/schemacs.md b/2025/talks/schemacs.md new file mode 100644 index 00000000..62ca5321 --- /dev/null +++ b/2025/talks/schemacs.md @@ -0,0 +1,90 @@ +[[!meta title="One year progress update Schemacs (formerly Gypsum)"]] +[[!meta copyright="Copyright © 2025 Ramin Honary"]] +[[!inline pages="internal(2025/info/schemacs-nav)" raw="yes"]] + +<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing --> +<!-- You can manually edit this file to update the abstract, add links, etc. ---> + + +# One year progress update Schemacs (formerly Gypsum) +Ramin Honary (he/him) - Pronunciation: "Rah-mean" (hard-H) "Ho-na-ree", Mastodon (preferred): ; blog: <https://tilde.town/~ramin_hal9001>; Codeberg: <https://codeberg.org/ramin_hal9001/schemacs> - SourceHut: <https://sr.ht/~ramin_hal9001> + + + +[[!inline pages="internal(2025/info/schemacs-before)" raw="yes"]] + +During EmacsConf 2024 last year I presented my work on a +clone of GNU Emacs written in Scheme which also clones the +Emacs Lisp programming language. In this talk, I will +briefly present an overview of the project similar to the +talk I gave last year, and then discuss the progress that +I have made on this project in the past year. + +To quote the description from the presentation I gave last +year: + +> Unlike other editors which only clone the Emacs +> keybindings (Edwin, Jed, jEdit, Jove, Lem, MG, Yi, +> Zile), I hope my Emacs clone will also fully clone the +> Emacs Lisp programming language well enough that many of +> the packages in ELPA, Non-GNU ELPA, and perhaps even +> MELPA, can be used in [Schemacs, formerly "Gypsum"] +> without any modification. I would also like to talk a +> little bit about how I am implementing it (the software +> architecture), and invite others to contribute. +> +> I think my project is of interest to many Emacs users +> because, firstly, I have personally spoken with a +> relatively large number of people who have expressed +> interest in making Emacs programmable in Scheme. +> Secondly, there is a good amount of prior art for Scheme +> implementations of Emacs. There are even builds of Emacs +> that link to Guile which provides a "scheme-eval" +> built-in function that translates between Elisp data +> types and Scheme data types. The Guile compiler itself +> ships with an Emacs Lisp compiler as well, although it +> does not provide enough of Emacs's built-in functions to +> be of much use. + +The progress I have made so far: + +- Ported all Guile-specific parts of the Emacs Lisp + interpreter to fully standards-compliant R7RS Scheme + code. The interpreter now runs on a few different + Scheme implementations, not just Guile. The GUI remains + Guile-only for now. + +- Implemented a new R7RS-compliant lexer and parser which + constructs an Abstract Syntax Tree (AST) data structure, + making it easier to find the source of errors and + produce informative back traces. + +- Implemented enough of the Emacs Lisp interpreter to be + able to load the "subr.el" source file, this defines + what you might call the "core" of the Emacs Lisp + language, including macros such as "defun" and "lambda." + +My primary goal continues to be to make it as easy as +possible for other people to contribute to this +project. Pretty soon it should be possible to run the +Emacs Regression Test suite (ERT) in the cloned Emacs Lisp +interpreter. Once this is done, we can run the same test +code used during the building and testing GNU Emacs to +test Schemacs. Hopefilly then, anyone will be able to +select a failing test, write code to make the test pass, +and submit a patch. + +About the speaker: + +I am Ramin Honary, I am have been professional software +engineer for 17 years and I have always had a passion for +functional programming languages, especially Haskell and +the Lisp family of languages. + + + +[[!inline pages="internal(2025/info/schemacs-after)" raw="yes"]] + +[[!inline pages="internal(2025/info/schemacs-nav)" raw="yes"]] + + diff --git a/2025/talks/weights.md b/2025/talks/weights.md new file mode 100644 index 00000000..06701453 --- /dev/null +++ b/2025/talks/weights.md @@ -0,0 +1,41 @@ +[[!meta title="Weightlifting Tracking with Emacs on Android"]] +[[!meta copyright="Copyright © 2025 Zachary Romero"]] +[[!inline pages="internal(2025/info/weights-nav)" raw="yes"]] + +<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing --> +<!-- You can manually edit this file to update the abstract, add links, etc. ---> + + +# Weightlifting Tracking with Emacs on Android +Zachary Romero - <https://zacromero.com/>, <mailto:zacromero@posteo.com> + +[[!inline pages="internal(2025/info/weights-before)" raw="yes"]] + +Emacs on Android opens up a world of new possibilities for replacing +proprietary software with free alternatives. One such use case is +using Emacs and org-mode to replace the popular weightlifting tracking +apps like Hevy and Strong. + +Org-mode provides a solid foundation to replicate these apps +functionalities but by itself is cumbersome to use in the middle of a +workout. With the help of Elisp however, we can provide an experience +as seamless as these paid apps, but with added flexibility and +freedom. + +This talk will go over the package itself as well as the way org-mode +can be used as the foundation for applications on top of it. + +About the speaker: + +I'm Zachary Romero, a software developer and Emacs enthusiast. I've +been weightlifting for about three years when I grew tired of the +many apps constantly trying to push subscriptions. Knowing the many +things org-mode can do, I set about trying to replicate the same +functionality in Emacs. + + +[[!inline pages="internal(2025/info/weights-after)" raw="yes"]] + +[[!inline pages="internal(2025/info/weights-nav)" raw="yes"]] + + diff --git a/2025/talks/zettelkasten.md b/2025/talks/zettelkasten.md new file mode 100644 index 00000000..63143bf8 --- /dev/null +++ b/2025/talks/zettelkasten.md @@ -0,0 +1,47 @@ +[[!meta title="Zettelkasten for Regular Emacs Hackers"]] +[[!meta copyright="Copyright © 2025 Christian Tietze"]] +[[!inline pages="internal(2025/info/zettelkasten-nav)" raw="yes"]] + +<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing --> +<!-- You can manually edit this file to update the abstract, add links, etc. ---> + + +# Zettelkasten for Regular Emacs Hackers +Christian Tietze (he) - [@ctietze@mastodon.social](https://mastodon.social/@ctietze) <https://christiantietze.de> <https://zettelkasten.de>, <mailto:hi@christiantietze.de> + +[[!inline pages="internal(2025/info/zettelkasten-before)" raw="yes"]] + +There's this one thing you can do with your Emacs that is not chiefly a technological problem to solve: thinking through writing. + +Emacs offers a malleable environment where you can tweak every key stroke, and every pixel on screen to your needs. Since we're all here at EmacsConf, the intention is clear: to use and enjoy Emacs, and spend our lives in this amazing environment. + +While it's easy to ditch modern UI conveniences and pull technology like email, chat, database and server management, and editing book drafts into Emacs – well, these are tasks that have been implemented, for which there exist alternatives, and which you can teach Emacs to do in a similar way. Oversimplifying, we can copy and tweak existing solutions. + +Now everyone's approach to <mark>thinking</mark> is a bit different, and there's no cookie cutter solution to merely rewrite in Emacs Lisp. Everyone needs to figure out how to do this on their own, and then find an implementation that suits their needs. (Including using paper, but we're not talking about paper here.) + +This is where I offer you one simple method to deep thinking, understanding, and problem solving: create yourself a Zettelkasten, an environment of linked notes that scales well over decades, so that you can take it with you into retirement and beyond for a lifelong journey of learning. + +For this talk, I assume that writing improves the quality and depth of thought. I also assume that you know how to type and move around in Emacs. The rest is just convention, and we'll walk through a couple of examples and exercises together so that after this talk, you're equipped with the simple tools that help you unlock new insights in your future.- Talk description (<= 500 words): +There's this one thing you can do with your Emacs that is not chiefly a technological problem to solve: thinking through writing. + +Emacs offers a malleable environment where you can tweak every key stroke, and every pixel on screen to your needs. Since we're all here at EmacsConf, the intention is clear: to use and enjoy Emacs, and spend our lives in this amazing environment. + +While it's easy to ditch modern UI conveniences and pull technology like email, chat, database and server management, and editing book drafts into Emacs – well, these are tasks that have been implemented, for which there exist alternatives, and which you can teach Emacs to do in a similar way. Oversimplifying, we can copy and tweak existing solutions. + +Now everyone's approach to <mark>thinking</mark> is a bit different, and there's no cookie cutter solution to merely rewrite in Emacs Lisp. Everyone needs to figure out how to do this on their own, and then find an implementation that suits their needs. (Including using paper, but we're not talking about paper here.) + +This is where I offer you one simple method to deep thinking, understanding, and problem solving: create yourself a Zettelkasten, an environment of linked notes that scales well over decades, so that you can take it with you into retirement and beyond for a lifelong journey of learning. + +For this talk, I assume that writing improves the quality and depth of thought. I also assume that you know how to type and move around in Emacs. The rest is just convention, and we'll walk through a couple of examples and exercises together so that after this talk, you're equipped with the simple tools that help you unlock new insights in your future. + +About the speaker: + +Creative macOS/iOS developer with a strong focus on user experience and clean architecture. Driven by a passion for accessibility and performance, I have published six apps and authored three technical books and 895 blog posts and counting. I help developers world-wide to realize their app ideas with a deep understand for the technologies they use. + + + +[[!inline pages="internal(2025/info/zettelkasten-after)" raw="yes"]] + +[[!inline pages="internal(2025/info/zettelkasten-nav)" raw="yes"]] + + |