@thedaemon What do you mean by #Lisp? There are at least a dozen dialects of Lisp in common use today, and literally hundreds in existence. #CommonLisp is only one of these.
@thedaemon What do you mean by #Lisp? There are at least a dozen dialects of Lisp in common use today, and literally hundreds in existence. #CommonLisp is only one of these.
#lisp When you have a working library, an easy way to get a terminal-based readline application in 2 lines:
https://dev.to/vindarel/common-lisp-a-command-line-interactive-terminal-application-in-2-lines-2gnb
short post, efficiency gains inside… how useful is it for you for the day-to-day? (honest question. Do you have many lisp utils you'd use on the terminal?)
#lisp Did you try sending emails in #commonlisp ? At first I didn't know how to use cl-smtp and I relied on Sendgrid's API. It's a good, maintained library, with no quick getting-started snippet. Here it is.
https://dev.to/vindarel/send-emails-with-common-lisp-smtp-gmail-sendgrid-mailgun-4aac
We mention trivial-imap too, that manages pop3 and IMAP folders, and even has a function to search emails.
I fuckin love this highly customizable, tweakable and hackable beast
#spatial #programming #commonLisp #leonardoCalculus
https://screwlisp.small-web.org/lispgames/LCKR-organisms-2/
New organisms-2 knowledgebase,starting out with local spatial walking at @mdhughes https://mdhughes.tech/ recommendation that fast access to local neighbors is fundamental.
I.e. I don't want to check every organism in the world to check who is standing next to me. Well, I put that in a knowledgebase in my organisms-2 #KRF here.
Seems to work, pulls in 8 connected and 24 connected neighbors rightly.
Hello guys! I'm returned before two weeks. There are the result of my NixOS setup.
There are some of my config files:
https://github.com/FrancoBujakiewicz/nixos-setup
@vnikolov @tusharhero @evgandr @mdhughes @screwlisp
For me the one true editor was a dos program, qedit.
When I went to Linux I chose gedit as the most functionally equivalent to qedit even if it didn't have the feature set. When gedit lost it's way I followed pluma down the fork.
I am learning Emacs as an IDE for common lisp. My guru is @screwlisp and I am trying to understand his document.
https://screwlisp.small-web.org/fundamental/installing-lisp-etc/
I am totally uninterested in the vim/emacs wars.
One last thing before I go to bed early... new development AppImage for #Benben is up :D x86-64 Linux, as usual.
https://chiselapp.com/user/MistressRemilia/repository/benben/wiki?name=Releases
#CommonLisp #LinuxAudio
@phil My personal preference is none of the Lisp-specific package managers. I use #Guix for managing all kinds of packages, including #CommonLisp. Guix also builds on ASDF, but also handles non-Lisp dependencies (mostly C libraries), which is nice.
@phil There are three layers to code management in #CommonLisp:
0. The language standard, which is very basic: you can load source code files.
1. ASDF, which manages "systems" (roughly collections of source code files, plus tests etc.) and their dependencies. If all the code you need is in your local file system, ASDF is all you need. It's also a de-facto standard, in that all modern implementations support it
2. Package managers, which download systems to the local file system.
<">
I think some people do either end up not using slime, or not using sbcl’s ext:save-lisp-and-die to save and resume their universe lisp image core when they are using slime. When you should use both.
</">
Good points.
I'll make a weaker statement.
You don't _have_ to use them.
Your mode of operation will vary.
But you must make an __informed__ decision whether to use them or not.
> As much as CL is 'standardized', it doesn't appear to have a standard way of interaction with the ecosystem.
Aside:
as a language, Common Lisp _is_ standardized, no quotes.
Yes, it is unfortunate that (official) standardization didn't get around to doing more.
Simplistically, blame it on the first AI winter.
I think most people's problem with Lisp is that it wins no popularity contests.
Like Shakespeare's Banquo from the Play, it begat kings though it was none.
#sbcl #commonLisp #slime #emacs #programming .
https://screwlisp.small-web.org/fundamental/sbcl-slime-eval-lisp-and-die/
I think some people do either end up not using slime, or not using sbcl’s ext:save-lisp-and-die to save and resume their universe lisp image core when they are using slime. When you should use both.
This article covers that.
On this 22nd day of the 7th month, 22/7 being a better approximation of π than 3.14, here is a curio due to P. Olivera (2005).
Take the fractional part of π, and sum the first 3 groups of 6 decimal digits: you get 1588419.
Skip the next 15 digits: 88419 follow.
Here is a #CommonLisp program to illustrate:
<https://vnikolov-lines.blogspot.com/2025/07/en-curio-about-digits-of-pi.html>.
Sources:
<https://mathworld.wolfram.com/PiDigits.html> (sets cookies)
via
<https://www.futilitycloset.com/2025/07/15/portent/>.
The Common Lisp implementation of Medley Interlisp is closer to CLtL1 than ANSI but does support the condition system. The CONDITIONGRAPH tool shows the hierarchy graph of conditions.
Unfortunately the state of graphics programming frameworks in #commonlisp is not quite there yet, so it seems I'll be crawling back to #cpp and #openframeworks for my graphics needs.
Bits and pieces are there in the lisp ecosystem, but there's nothing at the moment that ties it all together in the way that oF or Processing does. In the future I might think of going down the Clojure/quill route, as it seems I should be able to leverage the full power of a lisp and all of Java/Processing.
Installing lisp for beginners.
https://screwlisp.small-web.org/fundamental/installing-lisp-etc/
So much computing is predicated on having this or a conscious alternative decision to it. Here is my attempt to help beginners get this far. What do you think?
> ANSI CL does not call for or need TCO as such.
My impression is that the ANSI committee didn't want to burden implementors by mandating tail call elimination (it is easier in Scheme), but don't take my word for it.
Besides, a stack overflow can be of great help to tackle endless loops, though that is a different story.
> DO exists because it is exactly like one common case of TCO.
Yes.
By the way, TCO as a TLA sounds like an OS/MVS thing...
@deech For the practicalities of working with #CommonLisp, the Common Lisp Cookbook is a good resource:
@ksaj @pkw @deech
oh, yeah, good book.
When I first went to read the art of the metaobject protocol and I got to where it says "if you are new to the common lisp object system, go read Sonya Keene's Object-oriented Programming in Common LISP: A Programmer's Guide to CLOS now then come back afterwards"
but I made the mistake of trying to read AMOP first (which I did not much understand or retain). #AMOP #bookstodon #commonLisp