🚀 go-pugleaf

In article <C000Gt.BIs@NeoSoft.com> peter@NeoSoft.com (Peter da Silva) writes:
>In article <1992Dec28.182200.9740@ee.ryerson.ca> elf@ee.ryerson.ca (luis fernandes) writes:
>> peter@NeoSoft.com (Peter da Silva) writes:
>> >Well, I started to make a clock from one of those "build a working paper
>> >clock" books, but I got carried away. It's now a complete working paper
>> >Analytical Engine, and I run an 80386 simulator on that. I'm booting 386BSD
>> >now, and in a couple of years when it comes up I'll have Xclock running.
>> >I don't think it's going to keep very good time, though... I keep getting
>> >silo overflows reading WWV at 110 baud. I guess I'll need to build a paper
>> >16550 to fix that.
>
>> >Which Xclock should I use?
>
>> How 'bout one written in PostScript; sure you'd have to go
>> pick-up hardcopy every time you wanted to know the time & it
>> would consume enormous amounts of paper if you wanted updates
>> every second, but you'll have to agree it'd be really neat...
>
>How about this: I'll have it use Ghostscript to render a copy
>of the Working Paper Clock, and print that. Then I don't even need
>to run it!!!!!

Most ingenious! 
 
However, it would be most interesting if the printer ran a
multi-tasking OS (capable of 2 processes at least); the clock would
run in the background and the print-jobs would run in the
foreground.  The user would then be able to query the printer for
the time...

In view of this, I'm certainly looking forward to your entry in the
Obfuscated PostScript Contest...

--
elf@ee.ryerson.ca