Getting into https://lambda.moo.mud.org/ for the uninitiated, featuring #tintin++ #MUD client #lambdaMOO
apt install tintin++
tt++
#session moo lambda.moo.mud.org 8888
co guest
@join screwtape
"hey everyone!
:has opinions on what is being said live

@kentpitman @prahou @davidrevoy @bagder @chiply @yantar92 @jackdaniel @mdhughes

LambdaMOO

Introducing mine, a Coalton and Common Lisp IDE

By Robert Smith mine is a brand new IDE for Coalton and Common Lisp, built from the ground up with one purpose: To make Coalton and Common Lisp easier and more accessible to the programming world. TL;DR? Go to mine's homepage with downloads for Windows/macOS/Linux. mine is a complete, single-download application that comes with everything needed to experience the interactive and incremental development programming workflow, including hot-reloading and on-the-fly debugging, that Lisp programmers often refer to as the differentiating feature of the ecosystem. After installing, one can immediately open a file, program some Coalton or Lisp, and beam code to the REPL. On the same token, it has many of the advanced features you’d expect in a professional IDE:

The Coalton Programming Language
@reiver i maintained a fork of #lambdamoo called stunt for quite a long time. i spent some time thinking about how to build a ActivityPub-compatible MOO vocabulary for rooms, exits, objects, and actions/verbs on those things, as well as, maybe, building.
@mdhughes
I see your ed(1) and raise you @edit #lambdaMOO
@alexshendi

#lispyGopherClimate Tuesday-night-in-the-Americas

https://toobnix.org/w/88ZPfUcso2HNSKX6gNYShW #archive <- should have full audio

- This brave new world's #AI #vulns
+ #climateCrisis with e.g. oil

- The #commonLisp #conditionSystem #programming thread (& #shell ) https://gamerplus.org/@screwlisp/116390562771940285
Featuing @kentpitman @dougmerritt @vnikolov and more

- Also a note from @JohnMashey #unix when I tagged him (mostly, "haven't touched #lisp since the 70s").

- Live chat on #lambdaMOO !

@sdf can someone validate @artemis .

Junky summary of me running #lambdaMOO myself on a 64 bit system.

Simple details such that you can do exactly what I have done. Debugging mood, not a high-quality-writing mood.

https://lispy-gopher-show.itch.io/lispmoo2/devlog/1484719/lambdamooing-at-all-me-working-around-classic-32-bit-modern-64-bit-core-database-problem

#gamedev #devlog #mud .

The 32/64 database problem I think is that the change in integer width broke some listutils, which trivially stops @create and @dig working (important ones!) because the map_args over the aliases errors.

tl;dr
@edit #21:set_names
del #14
ins "return {name, {}};"

LambdaMOOing at all + me working around classic 32 bit -> modern 64 bit core database problem - lispmoo2 by screwtape

Primer on running lambdamoo on your lonesome : hacking the old 32 bit core databases work to some extent on 64 bit. https://github.com/wrog/lambdamoo?tab=readme-ov-file#user-content-legacy-database-su...

itch.io
@wrog
Hey, do you have an easy answer - why am I getting
#55:map_arg*s, line 13: Range error
?
To my knowledge I configured https://github.com/wrog/lambdamoo/?tab=readme-ov-file#user-content-legacy-database-support and have tried a range of core databases. #lambdaMOO
Stuff *not* calling that seems to work:
@dig "Someroom" -> #99
@go #99
@describe here as my room
look here
Chat on lambda.moo.mud.org as always please ! co guest @join mdh #lambdaMOO