Paolo AmorosoMarco Antoniotti @marcoxa released a new version of MK-DEFYSTEM, the venerable Common Lisp system construction tool, and shared some notes on the history of the project.
http://within-parens.blogspot.com/2026/04/an-update-on-mk-defsystem.html
Marco Antoniotti
charliemacI just realized I won't be able to stream when I usually do tomorrow, so I'm going to try to today. It's short notice, yet again, apologies...but about 1 hour from posting time, 10am CDT / 16:00 UTC, I get started.
https://www.twitch.tv/endparen
I plan on updating with upstream #McCLIM and previewing those, then will take stock of where I want to next focus.
vindarelLearn #commonlisp's low-level iteration constructs: do and do*, tagbody and go:
Deep PandyaJust completed the book "Common Lisp: A Gentle Introduction to Symbolic Computation" 1990 editon!
Recently, 3 months ago I started learning the basic of Lisp (inspired by reading Free As in Freedom 2.0), installed Emacs, Slime, SBCL and continued learning whenever I got some time.
Although my choice of book/stuff may be obsolete however I feel the learning is quite meaningful. Hoping for implementing/experimenting it further to some practical recognizable task.
screwlispThings got a little screwy, but I added parsing for the historic #sixel notation.
"P #0;2;3;4#3;2;3;4
#0abcde$
#0abcde-
#3abcde$
\\"
CL-USER> (with-input-from-string (in *) (read in))
(BASICALLY-SIXELS (#1=(1/50 3/100 1/25) #2=(1/50 3/100 1/25)) (#1# A B C D E $)
(#1# A B C D E -) (#2# A B C D E $))
That output e.g. renders sixels in a #mcclim application pane & also makes it clear why that macro looks how it does. #commonLisp #programming #unironic #retrocomputing
#lispyGopherClimate #ARCHIVE . https://toobnix.org/w/rCh5hUjPxVcXEBcnnVy37A
scroll down for #party
I fell into a powerfully deep funk, and screwed around in #McCLIM #commonLisp to more or less implement DEC's sixel printing to cheer myself up. https://lispy-gopher-show.itch.io/dl-roc-lisp/devlog/1475104/super-simple-lispised-dec-sixel-macro-for-common-lisp-inferface-manager @reiddragon
instead of doing anything I am meant to be doing.
#climateCrisis in the oil crisis notes + #haiku by @kentpitman
#lambdaMOO #aprilfools BYOB pool party tomorrow in the MOO 22 hours from now. I will set up after the show sometime
????
Sencha Wizard 🍵🧙♂️Finally got around to updating polydiceware to ECL. here is the path to it: https://codeberg.org/senchawizard/polydiceware #CommonLisp #Dice #Diceware
Vassil Nikolov | Васил НиколовI can connect to this Mastodon server now, so here is the reply I couldn't send yesterday.
I am indeed a satisfied customer of `read-delimited-list'.
In general I can only repeat, perhaps redundantly, the old advice that I myself found in Guy Steele's book:
to set things up, call `set-syntax-from-char' from right parenthesis to the chosen closing delimiter.
Typically do that in a copy of the system readtable, binding `*readtable*' to this copy.
Obviously,
(set-syntax-from-char #\) #\Newline)
drops any whitespacity from the latter (again, in a copy of the system readtable, if you try this at home), so reading all items to end of line in one go as a list is all portable and hunky-dory afterwards.
If there is another specific question as well, maybe I can be of more help.
Kira Verhovyh 
That was an intense amount of time... A month? I lost track. I decided to rewrite my custom #cffi c2ffi translator (https://github.com/keelah-mt/cl-kl-c2ffi) in #coalton 
I’ve been running on fumes this week, tbh I got quite irritated by how slow the rewrite was going. That has nothing to do with Coalton of course - it is an incredibly nice language. The problem is that this project is just a tool to support my #commonlisp #wgpu bindings, and I’ve made zero progress on that since I last posted... which I now see was Feb 27...
Anyway, the rewrite performs better. Unlike my first attempt, it parses Wayland/X11/GLFW almost completely. There is one manual fix I need to do to load the GLFW bindings, and that's good enough for now. I can finally switch from handwritten GLFW bindings to generated ones! Once that is done, I'll be ready to resume work on WGPU. 
Unless I get distracted by Coalton! 
What a nice language!
