@nsrahmad that's funny, I once did something similar, except I embedded a lisp "interpreter" into PHP rather than generating code.

ah yeah, system administration documentation or how I like to call it "~/.bash_history"

@praxeology Yeah, my favorite thing about the ecosystem is that it has a sort of culture that allows it to be ok for something to be "finished": when I was starting out, I was worried about apparently unmaintained libraries, but they haven't been the problem they would be in webdev or Python

@praxeology Yeah, my favorite thing about the ecosystem is that it has a sort of culture that allows it to be ok for something to be "finished": when I was starting out, I was worried about apparently unmaintained libraries, but they haven't been the problem they would be in webdev or Python

@jackdaniel@mastodon.social @luismbo Yeah, we're following each-other: I suspect the thing that toots his tweets doesn't know that

@nydel @phoe it makes it less painful to deal with lisp's penchant for multi-word function and variable names. The other thing that's helpful is doing something like sb:s-l-a-d, and it'll complete the package name as well, to sb-ext:save-lisp-and-die

@nydel @phoe this behavior of slime completion was one of the selling points for me

A little slime contrib (emacs mode for Common Lisp) I'm working on: open a stream from Lisp that streams data written to it to a dedicated Emacs buffer.

Code here (for now): github.com/fiddlerwoaroof/slim

I mean, Nouevau has not seen many improvements for some time now, I feel like community is finally growing tired of the ways NVIDIA treats them, and after seeing that there is a better way (that being AMD example from earlier).

Don't buy NVIDIA, please, for the love of god, this has to stop.

Show older
Mastodon @ SDF

"I appreciate SDF but it's a general-purpose server and the name doesn't make it obvious that it's about art." - Eugen Rochko