Turn the sound on! Though I was hoping that it would overstrike so much that it cut through the paper.
Actually <STRIKE>
Previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously.
An ASR33! Nice. I'm a little surprised a modern *nix can deal with it.
The plastic cover has been removed so that we can see (and hear!) the print mechanism in action.
Speaking about old shit, you mentioned in a previous post that you were having problems with compiling XEmacs. What is the legal status of the codebase? Can peeps hack on it without dealing with rmsemacs?
Not that I'm volunteering or anything...
It’s all GPL, but without copyright assignment to FSF.
Boring but relevant too; it’s now GPLv3, still without (an obligation to) assign copyright to the FSF. The XEmacs trunk doesn’t support Carbon or Cocoa, but should compile fine on recent macOS. Please get in touch with me (I am the main active XEmacs developer) if doesn't, my own OS X is old, but I am testing with recent compilers regularly.
Andrew Choi explicitly declared his Carbon code public domain, and then removed the GPL notices from files derived from GPLed code. The latter step was the stumbling block, it doesn’t look fantastic for respecting copyright, and as the XEmacs project we should have just ignored it twelve years ago and merged his code anyway, restoring the GPL notices. We didn’t, and here we are.
The pattern with people who turn their hand to emacs coding after experience somewhere else (Choi included) is that they make the effort with GNU Emacs, and if, at some point, they switch to XEmacs, their baseline level of stress suddenly goes down, as they encounter things like abstraction and encapsulation and reasonable design. Unfortunately, it turns out making good technical decisions is less good at attracting and keeping users and developers than is being, basically, a Biblical prophet with the poor mental health implicit in that.
If you’ve any interest it’s completely kosher to use the GNU code in XEmacs (from the FSF’s perspective and from ours), and there is a reasonable amount of GNU Cocoa code that could be ported without starting everything from scratch.
This taught me everything I know about teletypes.
Now I want one.
Thanks for linking to that playlist. That's great!
Nice! - brings back memories of Comp Sci 102 on DECWriter printer terminals.
C.
I started with learning BASIC on ASR33s connected to an HP minicomputer. Later the college I was at got DECwriter IIs and CRT terminals.
Fun with papertape. 🙂
I remember the late Steve Jobs talking about how he was in awe when that same thing would type code in his parents garage.
Does stty tty33 -lcase xcase -- or whatever it takes to get uppercase marked with backslashes -- screw up the overstrike?
please tell me that the driver was written in
bash.I'm imagining a FLOSS mailing list argument where a new submitter's patchset is rejected because it would add just enough objects to cause an extra "50% done" message in `git clone` and thus use too much ink in the teletype at the build farm.
Suddenly wondering if anyone has ever staged Leroy Anderson's "The Typewriter" on a Model 33.
So
'{background-opacity: 0}'should make the browser transparent to all the other windows behind and if you format your desktop image with such you should see the resistors and chips and whatever other contraband and crumpled up suicide notes they manage to smuggle out of the monitor factories.