#emacslisp — Public Fediverse posts

@csepp Here's a little thing I made to check for message body, subject line, and attachments. Works in message-mode, tested in #mu4e, should work under Gnus and others...?

https://codeberg.org/jamesendreshowell/gists/src/branch/master/jeh-message-lint.el

#emacslisp #emacs

https://github.com/eval-exec/neomacs

https://github.com/CeleritasCelery/rune

https://github.com/helix-editor/helix/pull/8675

At this rate, I wonder what will get completed first. Neomacs looks delicious though, ngl (even if vibecoded, I'm assuming it's a good one)

#emacs #steel #emacslisp #helix

I am going to give the PALE (Picture and Animation Library for Emacs) a try. Building it by hand, let’s see if I can get it working as a Linux Mint native build (no Guix or anything).

#tech #software #Emacs #Linux #Lisp #EmacsLisp #ProceduralGeneration

UPDATED BLOG POST: Finally tracked down and fixed a little bug in "Custom sorting of mu4e headers"

https://jamesendreshowell.com/2026-01-08-custom-sorting-of-mu4e-headers.html

#emacs #mu4e #emacslisp

I was able to finish reading all of “The Genius of Lisp“ by @cdegroot and the whole book was as good as the free preview (chapter 8). I was able to speed-read through the detailed explanations of concepts I already knew, like tail recursion, garbage collection, the Y-combinator, Currying functions, and so on. But there were parts where I slowed down and read carefully, like the section on the Universal Turing Machine, and some of the details of the IBM-704 system architecture. Also the story of how the first Lisp implementation was created when one of McCarthy’s grad students implemented an M-Expression calculator, this was described in slightly more detail than what I recall McCarthy himself explaining in his 1960 paper — that or I had just forgotten those parts of the story.

The tone of this book reminds me a lot of popular physics books like Stephen Hawking’s “A Brief History of Time,” which was aimed more at general audiences than professionals. That said, there is a lot to enjoy about this book for professionals like myself as well. There are many good stories about the principals designers of Lisp throughout. The sections on the commercialization of Lisp for the first AI boom of the 1970s and it’s subsequent “AI winter,” were very interesting to read. And if you are a teacher, you might like how some of the concepts in the book are explained.

And I would definitely recommend this very strongly to 3rd-year high school students, or 1st and 2nd year college students, who are more genuinely curious about how computers work and want to know more than just how to make the next billion dollar app.

The next #LispyGopherClimate show with @screwlisp I look forward to talking about this book some more.

#tech #software #Lisp #ProgrammingLanguages #SchemeLang #Scheme #Clojure #Emacs #EmacsLisp #RetroComputing #LispyGopherClimateShow

I've not really posted anything on my #blog for a while, and one of the reasons was that every time I tried to, I ended up having to work on catching up on a bunch of #hugo changes before the blog would build because inevitable on one of my four "main" machines, the blog wouldn't build due to some backward-incompatible changes.

Any recommendation for a static site generator that takes backward compatibility a bit more seriously? I've used #Jekyll in the past but I haven't looked into the state of that ecosystem for years.

My strong preference would be for a static site generator written in #clojure, #ClojureScript, #CommonLisp or #emacslisp. Preferably one that integrates well with #isso for comments.

Not interested in a more "dynamic" system like Ghost - I moved away from WordPress quite a while ago to reduce the amount of maintenance and attack surface, and I don't want to go back.

I've not really posted anything on my #blog for a while, and one of the reasons was that every time I tried to, I ended up having to work on catching up on a bunch of #hugo changes before the blog would build because inevitable on one of my four "main" machines, the blog wouldn't build due to some backward-incompatible changes.

Any recommendation for a static site generator that takes backward compatibility a bit more seriously? I've used #Jekyll in the past but I haven't looked into the state of that ecosystem for years.

My strong preference would be for a static site generator written in #clojure, #ClojureScript, #CommonLisp or #emacslisp. Preferably one that integrates well with #isso for comments.

Not interested in a more "dynamic" system like Ghost - I moved away from WordPress quite a while ago to reduce the amount of maintenance and attack surface, and I don't want to go back.

I've not really posted anything on my #blog for a while, and one of the reasons was that every time I tried to, I ended up having to work on catching up on a bunch of #hugo changes before the blog would build because inevitable on one of my four "main" machines, the blog wouldn't build due to some backward-incompatible changes.

Any recommendation for a static site generator that takes backward compatibility a bit more seriously? I've used #Jekyll in the past but I haven't looked into the state of that ecosystem for years.

My strong preference would be for a static site generator written in #clojure, #ClojureScript, #CommonLisp or #emacslisp. Preferably one that integrates well with #isso for comments.

Not interested in a more "dynamic" system like Ghost - I moved away from WordPress quite a while ago to reduce the amount of maintenance and attack surface, and I don't want to go back.

I've not really posted anything on my #blog for a while, and one of the reasons was that every time I tried to, I ended up having to work on catching up on a bunch of #hugo changes before the blog would build because inevitable on one of my four "main" machines, the blog wouldn't build due to some backward-incompatible changes.

Any recommendation for a static site generator that takes backward compatibility a bit more seriously? I've used #Jekyll in the past but I haven't looked into the state of that ecosystem for years.

My strong preference would be for a static site generator written in #clojure, #ClojureScript, #CommonLisp or #emacslisp. Preferably one that integrates well with #isso for comments.

Not interested in a more "dynamic" system like Ghost - I moved away from WordPress quite a while ago to reduce the amount of maintenance and attack surface, and I don't want to go back.

I have been banging my head against #Gtk3 for the past 3 weeks and all progress has pretty much come to a stand-still. No matter how simple and straight-forward my GUI is, Gtk makes it simply impossible to get the layout correct. I am now convinced that programming my own layout algorithm from scratch and using the GtkLayout container (which lets you place widgets at arbitrary X,Y coordinates) is the only way to proceed at this point. It is soooo frustrating.

The #Gtk documentation is good, but not at all good enough. The people on the Gnome Discourse have been very kind and helpful, and I truly appreciate the engagement I have had there, but ultimately I am still not able to solve my problems.

I have decided I need find some way to keep making progress without postponing the release of the work I have done so far for an indeterminate length of time. So rather than work out all the bugs in this version before merging it to the main Git branch, what I will do instead is have the main program launch a debugger window. The debugger window will have all layout calculated in advance, and all widgets will be declared once and only once throughout the lifetime of the application to avoid the reference counting issues. Obviously the debugger GUI will be very rigid, but you will at least be able to edit files and run commands in a REPL within this debugger.

Then maybe I can merge the code I have written to the main Git branch, and people will at least be able to use it through the debugger. Maybe also I could use this debugger to help with writing my layout algorithm. Also, I need to get back to the Emacs Lisp interpreter, I haven’t worked on it in almost two months now.

#tech #software #Lisp #Emacs #EmacsLisp #Scheme #SchemeLang #R7RS

NEW BLOG POST: Custom sorting of mu4e headers

I love mu4e for dealing with email under Emacs: with a little Emacs Lisp you can make it do email how you want to do email.

https://jamesendreshowell.com/2026-01-08-custom-sorting-of-mu4e-headers.html

#emacs #mu4e #emacslisp

🎩✨ Behold the riveting saga of speculative JIT compilation in Emacs Lisp with Java—where Kyou is Kyou, and EmacsConf 2025 attendees pretend to care. 💤🤖 Enjoy this journey through the infinite loops of Lisp jargon that only the author and their cat will ever comprehend. 🐱📚
https://kyo.iroiro.party/en/posts/juicemacs-exploring-jit-for-elisp/ #EmacsLisp #JITCompilation #EmacsConf2025 #LispJargon #CatLovers #HackerNews #ngated

During the Emacs meetup yesterday, we started talking about Emacs LISP (of course) and I mentioned that I first learned LISP years (decades) ago. I was asked what version of LISP this was and I could not answer. So I've looked into this, just out curiosity.

I learned LISP on a mainframe (Amdahl 470V/6), an IBM plug compatible system. This system ran the Michigan Terminal System as its operating system. The version of LISP available on this system was 1.5, according to Wikipedia: see link below and, in particular, reference 92 in the list at the end of the page.

As an aside, I loved MTS. Very impressive time sharing system, supporting hundreds of simultaneous terminal users (with the aid of what were called *front end communications processors*).

https://en.wikipedia.org/wiki/Michigan_Terminal_System

#Emacs #LISP #EmacsLISP #MTS #MichiganTerminalSystem #Amdahl #Wikipedia

During the Emacs meetup yesterday, we started talking about Emacs LISP (of course) and I mentioned that I first learned LISP years (decades) ago. I was asked what version of LISP this was and I could not answer. So I've looked into this, just out curiosity.

I learned LISP on a mainframe (Amdahl 470V/6), an IBM plug compatible system. This system ran the Michigan Terminal System as its operating system. The version of LISP available on this system was 1.5, according to Wikipedia: see link below and, in particular, reference 92 in the list at the end of the page.

As an aside, I loved MTS. Very impressive time sharing system, supporting hundreds of simultaneous terminal users (with the aid of what were called *front end communications processors*).

https://en.wikipedia.org/wiki/Michigan_Terminal_System

#Emacs #LISP #EmacsLISP #MTS #MichiganTerminalSystem #Amdahl #Wikipedia

During the Emacs meetup yesterday, we started talking about Emacs LISP (of course) and I mentioned that I first learned LISP years (decades) ago. I was asked what version of LISP this was and I could not answer. So I've looked into this, just out curiosity.

I learned LISP on a mainframe (Amdahl 470V/6), an IBM plug compatible system. This system ran the Michigan Terminal System as its operating system. The version of LISP available on this system was 1.5, according to Wikipedia: see link below and, in particular, reference 92 in the list at the end of the page.

As an aside, I loved MTS. Very impressive time sharing system, supporting hundreds of simultaneous terminal users (with the aid of what were called *front end communications processors*).

https://en.wikipedia.org/wiki/Michigan_Terminal_System

#Emacs #LISP #EmacsLISP #MTS #MichiganTerminalSystem #Amdahl #Wikipedia

During the Emacs meetup yesterday, we started talking about Emacs LISP (of course) and I mentioned that I first learned LISP years (decades) ago. I was asked what version of LISP this was and I could not answer. So I've looked into this, just out curiosity.

I learned LISP on a mainframe (Amdahl 470V/6), an IBM plug compatible system. This system ran the Michigan Terminal System as its operating system. The version of LISP available on this system was 1.5, according to Wikipedia: see link below and, in particular, reference 92 in the list at the end of the page.

As an aside, I loved MTS. Very impressive time sharing system, supporting hundreds of simultaneous terminal users (with the aid of what were called *front end communications processors*).

https://en.wikipedia.org/wiki/Michigan_Terminal_System

#Emacs #LISP #EmacsLISP #MTS #MichiganTerminalSystem #Amdahl #Wikipedia

Emacs agent-shell (powered by ACP)

https://xenodium.com/introducing-agent-shell

#HackerNews #Emacs #agent-shell #ACP #EmacsLisp #programming #tools

Silent upgrade: Whisper Engine 0.1.0
Incremental site builds + cryptographic precision.
The web goes stealth.

#WhisperEngine #EmacsLisp #Emacs #DeadSwitch

I use Emacs with a modified inferior Lisp to access uLisp over serial on my Cardputer uLisp Machine. Any idea why I get extra ^Ms in the inferior Lisp?

The code of the modified mode and the full context is in this uLisp forum thread. Calling comint-strip-ctrl-m doesn't seem to help.

http://forum.ulisp.com/t/emacs-for-programming/236/15

#uLisp #EmacsLisp #Emacs

Wrote a post about my Emacs plugin, which helps to write posts for static blog right with #OrgMode
No more Markdown, web WYSIWYG editors and other stuff to compose blogposts — just one #Emacs to publish them all!

https://eugene-andrienko.com/en/it/2024/12/01/emacs-plugin-jekyll-blog

#emacslisp #lisp #StaticWebsites

@mcepl @dekkzz76
I am not sure honestly that the language emacs lisp is lacking so much. But I am not an expert. AFAIK the guile thing was done at a point where there was no native compilation for #EmacsLisp , which we now have thanks to #libgcc. The feeling of the 90s, I don't know, I like the style of #emacs personally but if you want something mor# flashy maybe take a look at #DoomEmacs or #SpaceMacs, of course it won't be vscode but well. There are projects also like #CliMacs but well..

On #Friendica and #Telegram:

›Call for Papers — 16th European #Lisp Symposium — #ELSConf —#Amsterdam — 2023-04-24/25‹

🔗 Friendica: https://libranet.de/display/0b6b25a8-1763-a88a-e526-72b275177682

🦎 Telegram: https://t.me/FamilyOfLisp/309

🌺

🏷️ #CommonLisp #Scheme #EmacsLisp #Clojure #Racket #ACL2 #AutoLisp #ISLISP #DylanLang #SKILL #Hy #Shen #Carp #Janet #Jank #uLisp #Picolisp #Gamelisp #TXR #FunctionalProgramming #AMOP #SICP #CLOS #PAIP #CLtL2 #AIMA #Emacs #VIM #LispWorks #AllegroCommonLisp #ACL #CLISP #SBCL #MetaObject #MetaObjectSystem

I think "koan"-style tutorials are a great way to kick the tires on a new programming language -- you're presented with suites of failing tests, and by fixing the tests you're taken on a tour of the language.

I helped convert the #CommonLisp #koans to #EmacsLisp awhile back -- if you like TDD and want to learn elisp tis a solid resource.

https://github.com/jtmoulia/elisp-koans

(annnd happy to provide support if things break, honestly haven't brushed the dust off it in a bit)

#Elisp #emacs #projects

@sigue

Btw, maybe you would like to join this Lisp Telegram group:

→ https://t.me/FamilyOfLisp

🌺

🏷️ #DylanLang #CommonLisp #Lisp #Scheme #Racket #ELSConf #Clojure #AutoLisp #ISLisp #EuLisp #Emacs #EmacsLisp #AMOP #CLOS #PMD #MultiLisp #qLisp #StarLisp #ConnectionMachine #ConnectionMachineLisp #SExpr