#lispm — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #lispm, aggregated by home.social.
-
So, I made the progress to (almost) bootstrap the Open Genera #lispM but accidentally rm -rf'd the working fep disk and world files. Time to verify if the setup can be reproducible 😹 . Anyway I uploaded my patched Genera world file for Arm64 on https://ldbeth.sdf.org and you can try it out with my patched VLM.
-
So, I made the progress to (almost) bootstrap the Open Genera #lispM but accidentally rm -rf'd the working fep disk and world files. Time to verify if the setup can be reproducible 😹 . Anyway I uploaded my patched Genera world file for Arm64 on https://ldbeth.sdf.org and you can try it out with my patched VLM.
-
So, I made the progress to (almost) bootstrap the Open Genera #lispM but accidentally rm -rf'd the working fep disk and world files. Time to verify if the setup can be reproducible 😹 . Anyway I uploaded my patched Genera world file for Arm64 on https://ldbeth.sdf.org and you can try it out with my patched VLM.
-
So, I made the progress to (almost) bootstrap the Open Genera #lispM but accidentally rm -rf'd the working fep disk and world files. Time to verify if the setup can be reproducible 😹 . Anyway I uploaded my patched Genera world file for Arm64 on https://ldbeth.sdf.org and you can try it out with my patched VLM.
-
Who wants to buy me a keyboard?
https://keymacs.com/product.html?a624n
€6,878 🤣
For that I can build someone a #LispMachine #LispM with a support contract ..
-
Who wants to buy me a keyboard?
https://keymacs.com/product.html?a624n
€6,878 🤣
For that I can build someone a #LispMachine #LispM with a support contract ..
-
Who wants to buy me a keyboard?
https://keymacs.com/product.html?a624n
€6,878 🤣
For that I can build someone a #LispMachine #LispM with a support contract ..
-
I couldn't find a copy of the memo named "Loop Iteration Macro" by Glenn Burke and David Moon, January 1981 (MIT/LCS/TM-169) at MIT's dSpace site, or anywhere else. So I scanned in my copy and have uploaded it to my web site.
NOTE WELL: This document was written prior to CLTL and describes a facility that was available in MACLISP and the Lisp Machine's Zetalisp. Common Lisp drew design ideas from this, but the syntax, semantics, and associated functions/macros described in this are NOT the same as what Common Lisp offers.
For example, my recollection from long ago (which I did not re-check before making this post) is that there are other differences in syntax because this earlier version of Loop was underconstrained in the ordering of the keywords in a way that let you write some expressions that the committee felt might confuse people with their results.
But also, for reasons that slip my mind, Common Lisp did not adopt the define-loop-path macro that is described starting on page 19.
http://nhplace.com/kent/History/maclisp/MIT-LCS-TM-169-Loop-Iteration-Macro.pdf
#lisp #maclisp #loop #iteration #ComputerHistory #KentsHistoryProject #lisp #LispM #Zetalisp #CommonLisp
cc @screwlisp
-
I couldn't find a copy of the memo named "Loop Iteration Macro" by Glenn Burke and David Moon, January 1981 (MIT/LCS/TM-169) at MIT's dSpace site, or anywhere else. So I scanned in my copy and have uploaded it to my web site.
NOTE WELL: This document was written prior to CLTL and describes a facility that was available in MACLISP and the Lisp Machine's Zetalisp. Common Lisp drew design ideas from this, but the syntax, semantics, and associated functions/macros described in this are NOT the same as what Common Lisp offers.
For example, my recollection from long ago (which I did not re-check before making this post) is that there are other differences in syntax because this earlier version of Loop was underconstrained in the ordering of the keywords in a way that let you write some expressions that the committee felt might confuse people with their results.
But also, for reasons that slip my mind, Common Lisp did not adopt the define-loop-path macro that is described starting on page 19.
http://nhplace.com/kent/History/maclisp/MIT-LCS-TM-169-Loop-Iteration-Macro.pdf
#lisp #maclisp #loop #iteration #ComputerHistory #KentsHistoryProject #lisp #LispM #Zetalisp #CommonLisp
cc @screwlisp
-
I couldn't find a copy of the memo named "Loop Iteration Macro" by Glenn Burke and David Moon, January 1981 (MIT/LCS/TM-169) at MIT's dSpace site, or anywhere else. So I scanned in my copy and have uploaded it to my web site.
NOTE WELL: This document was written prior to CLTL and describes a facility that was available in MACLISP and the Lisp Machine's Zetalisp. Common Lisp drew design ideas from this, but the syntax, semantics, and associated functions/macros described in this are NOT the same as what Common Lisp offers.
For example, my recollection from long ago (which I did not re-check before making this post) is that there are other differences in syntax because this earlier version of Loop was underconstrained in the ordering of the keywords in a way that let you write some expressions that the committee felt might confuse people with their results.
But also, for reasons that slip my mind, Common Lisp did not adopt the define-loop-path macro that is described starting on page 19.
http://nhplace.com/kent/History/maclisp/MIT-LCS-TM-169-Loop-Iteration-Macro.pdf
#lisp #maclisp #loop #iteration #ComputerHistory #KentsHistoryProject #lisp #LispM #Zetalisp #CommonLisp
cc @screwlisp
-
I couldn't find a copy of the memo named "Loop Iteration Macro" by Glenn Burke and David Moon, January 1981 (MIT/LCS/TM-169) at MIT's dSpace site, or anywhere else. So I scanned in my copy and have uploaded it to my web site.
NOTE WELL: This document was written prior to CLTL and describes a facility that was available in MACLISP and the Lisp Machine's Zetalisp. Common Lisp drew design ideas from this, but the syntax, semantics, and associated functions/macros described in this are NOT the same as what Common Lisp offers.
For example, my recollection from long ago (which I did not re-check before making this post) is that there are other differences in syntax because this earlier version of Loop was underconstrained in the ordering of the keywords in a way that let you write some expressions that the committee felt might confuse people with their results.
But also, for reasons that slip my mind, Common Lisp did not adopt the define-loop-path macro that is described starting on page 19.
http://nhplace.com/kent/History/maclisp/MIT-LCS-TM-169-Loop-Iteration-Macro.pdf
#lisp #maclisp #loop #iteration #ComputerHistory #KentsHistoryProject #lisp #LispM #Zetalisp #CommonLisp
cc @screwlisp
-
You can pick up the document 'Signalling and Handling Conditions' from this index page:
It was longer than I thought it would be, but I think you'll find it interesting to see what the Zetalisp condition system (which inspired the Common Lisp condition system) looked like.
In spirit, it was much the same. The biggest differences are:
* The CL system has 'active' restarts, where the ZL system had a passive thing where you returned a value to the case context and hoped that it would do the thing you wanted. It felt quite a bit more error-prone (if you'll pardon the reuse of 'error' here, maybe I should say 'mistake-prone').
* The ZL condition system offers a lot of really low-level stuff that did not seem proper for CL.
* The set of operations offered in ZL was richer, but also a lot more complicated, I thought, and I worried people would not really see what it was trying to do.
* Obviously, the ZL system was based on Flavors, not CLOS, and made reference to a lot of LispM-specific packages.
* The document was published in January, 1983 and identifies itself as part of Symbolics Release 4.0.
There are other differences as well.
#Zetalisp #LispMachine #LispMachines #Symbolics #LispM
#ConditionHandling #ConditionSystem #ErrorSystem #ErrorHandling #CommonLisp #CL #Flavors #CLOS #History #ComputerHistory
#InternetArchive #Bitsavers -
You can pick up the document 'Signalling and Handling Conditions' from this index page:
It was longer than I thought it would be, but I think you'll find it interesting to see what the Zetalisp condition system (which inspired the Common Lisp condition system) looked like.
In spirit, it was much the same. The biggest differences are:
* The CL system has 'active' restarts, where the ZL system had a passive thing where you returned a value to the case context and hoped that it would do the thing you wanted. It felt quite a bit more error-prone (if you'll pardon the reuse of 'error' here, maybe I should say 'mistake-prone').
* The ZL condition system offers a lot of really low-level stuff that did not seem proper for CL.
* The set of operations offered in ZL was richer, but also a lot more complicated, I thought, and I worried people would not really see what it was trying to do.
* Obviously, the ZL system was based on Flavors, not CLOS, and made reference to a lot of LispM-specific packages.
* The document was published in January, 1983 and identifies itself as part of Symbolics Release 4.0.
There are other differences as well.
#Zetalisp #LispMachine #LispMachines #Symbolics #LispM
#ConditionHandling #ConditionSystem #ErrorSystem #ErrorHandling #CommonLisp #CL #Flavors #CLOS #History #ComputerHistory
#InternetArchive #Bitsavers -
You can pick up the document 'Signalling and Handling Conditions' from this index page:
It was longer than I thought it would be, but I think you'll find it interesting to see what the Zetalisp condition system (which inspired the Common Lisp condition system) looked like.
In spirit, it was much the same. The biggest differences are:
* The CL system has 'active' restarts, where the ZL system had a passive thing where you returned a value to the case context and hoped that it would do the thing you wanted. It felt quite a bit more error-prone (if you'll pardon the reuse of 'error' here, maybe I should say 'mistake-prone').
* The ZL condition system offers a lot of really low-level stuff that did not seem proper for CL.
* The set of operations offered in ZL was richer, but also a lot more complicated, I thought, and I worried people would not really see what it was trying to do.
* Obviously, the ZL system was based on Flavors, not CLOS, and made reference to a lot of LispM-specific packages.
* The document was published in January, 1983 and identifies itself as part of Symbolics Release 4.0.
There are other differences as well.
#Zetalisp #LispMachine #LispMachines #Symbolics #LispM
#ConditionHandling #ConditionSystem #ErrorSystem #ErrorHandling #CommonLisp #CL #Flavors #CLOS #History #ComputerHistory
#InternetArchive #Bitsavers -
You can pick up the document 'Signalling and Handling Conditions' from this index page:
It was longer than I thought it would be, but I think you'll find it interesting to see what the Zetalisp condition system (which inspired the Common Lisp condition system) looked like.
In spirit, it was much the same. The biggest differences are:
* The CL system has 'active' restarts, where the ZL system had a passive thing where you returned a value to the case context and hoped that it would do the thing you wanted. It felt quite a bit more error-prone (if you'll pardon the reuse of 'error' here, maybe I should say 'mistake-prone').
* The ZL condition system offers a lot of really low-level stuff that did not seem proper for CL.
* The set of operations offered in ZL was richer, but also a lot more complicated, I thought, and I worried people would not really see what it was trying to do.
* Obviously, the ZL system was based on Flavors, not CLOS, and made reference to a lot of LispM-specific packages.
* The document was published in January, 1983 and identifies itself as part of Symbolics Release 4.0.
There are other differences as well.
#Zetalisp #LispMachine #LispMachines #Symbolics #LispM
#ConditionHandling #ConditionSystem #ErrorSystem #ErrorHandling #CommonLisp #CL #Flavors #CLOS #History #ComputerHistory
#InternetArchive #Bitsavers -
#lisp Kent M Pitman visual demo of 1984 #lispm Cross Referenced Editing Facility program for OpenUniversity #programming
-
#lisp Kent M Pitman visual demo of 1984 #lispm Cross Referenced Editing Facility program for OpenUniversity #programming
-
#lisp Kent M Pitman visual demo of 1984 #lispm Cross Referenced Editing Facility program for OpenUniversity #programming
-
@weekend_editor @charliemac @[email protected] @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 @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 @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
-
@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.
-
@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.
-
@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.
-
@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.
-
@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.
-
@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.
-
@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.
-
@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.
-
@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).
-
Current work in #LispMachine world is to implement the bus interface for the CADR 4 project (https://github.com/ams/cadr4).
-
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.
-
@vv I wish I could find those programs and restore them. 😞
There are plenty of fun ones, like the 3D airplane model.
-
@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).
-
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).
-
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).
-
Someone should write some #MIT #CADR microcode and supporting code to make it possible to run #Interlisp / #Medley on the #MIT #LispMachine #LispM
-
Someone should write some #MIT #CADR microcode and supporting code to make it possible to run #Interlisp / #Medley on the #MIT #LispMachine #LispM
-
Someone should write some #MIT #CADR microcode and supporting code to make it possible to run #Interlisp / #Medley on the #MIT #LispMachine #LispM
-
CADR4 #MIT #CADR #LispMachine #LispM is now running almost through the whole boot PROM!
Now work to add disk, and memory .. and a bus.
-
CADR4 #MIT #CADR #LispMachine #LispM is now running almost through the whole boot PROM!
Now work to add disk, and memory .. and a bus.
-
CADR4 #MIT #CADR #LispMachine #LispM is now running almost through the whole boot PROM!
Now work to add disk, and memory .. and a bus.
-
Agentic one promoting the #MIT #CADR #LispMachine #LispM.
-
Agentic one promoting the #MIT #CADR #LispMachine #LispM.
-
Agentic one promoting the #MIT #CADR #LispMachine #LispM.
-
CADR4 project is steaming a head. Things have started going through the boot PROM... #LispMachine #LispM #CADR
-
CADR4 project is steaming a head. Things have started going through the boot PROM... #LispMachine #LispM #CADR
-
CADR4 project is steaming a head. Things have started going through the boot PROM... #LispMachine #LispM #CADR
-
@lfa https://tumbleweed.nu/lm-3 #LispMachine revolution is nigh! #CADR #LispM.
-
@lfa https://tumbleweed.nu/lm-3 #LispMachine revolution is nigh! #CADR #LispM.
-
@lfa https://tumbleweed.nu/lm-3 #LispMachine revolution is nigh! #CADR #LispM.
-
@lfa I've been restoring / working on the #MIT #CADR #LispMachine #LispM for .. 20+ years now. I've never had the real thing, there are maybe four machines left in the world. N/A?
-
@lfa I've been restoring / working on the #MIT #CADR #LispMachine #LispM for .. 20+ years now. I've never had the real thing, there are maybe four machines left in the world. N/A?