It seems to me, though I can't quite tell, that you require
(assert (equal ds (pathname-directory (make-pathname :directory ds))))
for all appropriate values of `ds' (modulo typos).
It seems to me, though I can't quite tell, that you require
(assert (equal ds (pathname-directory (make-pathname :directory ds))))
for all appropriate values of `ds' (modulo typos).
[1/2] In #CommonLisp, SBCL accepts directory pathname components which are subpaths and not names:
(make-pathname :directory '(:absolute "tmp" "foo/bar")) returns #P"/tmp/foo/bar/".
On CCL, the same form yields #P"/tmp/foo\\/bar/" which of course results in errors in a lot of contexts because "/" is not a valid character in filenames.
Apparently I was working on a Common Lisp Unix shell two years ago as a fun project.
It is just minimally functional but maybe it'll make someone laugh, so I've uploaded it to Codeberg.
#CommonLisp #peertube #LIVE talking to @kasper about his #lispgames #gamejam cl- #opengl cl- #sdl2 podracer game #gamedev .
Sorry about all the sharpsigns. Also, I have no idea what chat I should try and look at.
#embeddableCommonLisp's #ffi (*not* libffi) #commonLisp #Cxx #programming example - taking base64 encoding C++ function/namespace from @jeremy_list 's secure scuttlebutt implementation, and using it for extremely portable common lisp rather than nonportable haikuos C++. A straightforward but technical indicative example.
https://screwlisp.small-web.org/fundamental/cxx-embeddable-common-lisp-habitat/
Though! My one seems to get half the out bytes wrong x_x Edit: I forgot three cdrs, now works 100%.
New blog post: Benben 0.7.0 Feature and Changes Overview
https://remilia.sdf.org/blog/2025-08-02-a.html
#benben #LinuxAudio #blog #vgm #CommonLisp #lisp
Back on my little #Trial game project after many months, fidgeting with particle emitters
@screwlisp wrote:
> about #commonLisp #indie #gameDev (w/ #opengl iirc) at 8pm NZT tomorrow
Isn't that 08:00 zulu (Sunday, August 3)?
What is the audio channel for it?
@awkravchuk hey, I'm going to talk to @kasper about #commonLisp #indie #gameDev (w/ #opengl iirc) at 8pm NZT tomorrow which I believe to be between between 8am and 12pm Sunday morning in much of Europe.
Kasper mentioned they would like to co-guest with you if you would like that (at admittedly short notice).
I think I missed a big announcement by you at some point previously as well. Would you like to visit / check in (in a one hour jitsi call #peertube #live #fedi)
#ecl #commonLisp #openbsd #port - a #Cxx #programming openbsd port (i.e. #ports #bsd #Makefile ). Discussion of #OS ports and the role of underlying operating systems in lisp, and a little about embedding embeddable common lisp in C++ and embedding C++ in embeddable common lisp.
https://screwlisp.small-web.org/fundamental/cxx-ecl-openbsd-port/
@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?)
#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.
@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.
<">
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.
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?