Lispy Gopher Climate w/ screwlisp#lisp Kent M Pitman visual demo of 1984 #lispm Cross Referenced Editing Facility program for OpenUniversity #programming
PeerTube
screwlisp#lispyGopherClimate Sunday morning in Europe with #lisp # live @kentpitman
Going over proto #emacs, #cref, #lispm #computerScience #softwareEngineering #GUI history ! Ask questions in #lisp on #irc now please !
https://toobnix.org/w/gXLXQqxf5MYg1NDF2Ua6oA 15 minutes to live.
https://communitymedia.video/w/h1jdbHm8xTj5VEDuCWAbBW
#lispyGopherClimate #technology #podcast #weekly
featuring @kentpitman @ramin_hal9001 @jns
Longterm #reliability , the #climateCrisis , technology and knowledge
Kent has found the source to his Cross referenced editing facility from Open University #lisp #lispm example.
#scifi #books with this theme? Ending of Cats Cradle?
On the #art side check, @prahou 's #unix_surrealism, https://photronic.art
Happy #lambdaMOO year! 35 years! https://lambda.moo.mud.org as always.
Zach 🇮🇱 🇺🇸@weekend_editor @charliemac @symbolics @restorante @crandel @Zenie @weavejester correct, I do recall, ‘sheet’ was the core abstraction in the #LispM window system. #CLIM made that a first-class concept, and #McCLIM still carries it forward today
Weekend Editor@amszmidt @restorante @demiguru @crandel @[email protected] @weavejester
> And the editor on #LispM is called ZWEI.
Well, technically... :-)
ZWEI (Zwei Was Eine Initially) was the infrastructure for writing editors, while the actual editor on the lispm was called Zmacs. In practice, nobody messed with Zwei unless they were extending Zmacs.
I have no experience of Eine, or at least no memory of it.
And yes, Zmacs was different from Gnu Emacs, which was different from all the other Emacsen before it.
Alfred M. Szmidt@restorante > Emacs in Unix possibly is different with Emacs (EINE, ZWEINE) on Lisp Machine.
Absolute nonsense. Stop confusing GNU Emacs, an implementation of Emacs, plus many other things.
And the editor on #LispM is called ZWEI.
@demiguru @restorante @crandel @alerque @[email protected] @weavejester
There is so much confusion in this thread that I don't know where to even start.
And no, #LispM did NOT expose the "whole stack as live, editable Lisp".
Emacs and GNU Emacs are also worth keeping separate when talking about these topics.
Current work in #LispMachine world is to implement the bus interface for the CADR 4 project (https://github.com/ams/cadr4).
@vv I wish I could find those programs and restore them. 😞
There are plenty of fun ones, like the 3D airplane model.
CADR4 #MIT #CADR #LispM #LispMachine current status is we are optimizing the simulation runtime (it takes about 10 minutes to run through almost all the boot PROM to the point we are accessing memory -- which isn't fun when you want to work on accessing memory).