90 Followers
93 Following
813 Posts
a shadow in the wall
alter ego@pesco

PS:
Total length of the document is 126 pages (all of chapter 5). I have not tracked time exactly, but it took more than 60 and less than 100 hours, spread across 4.5 weeks in a three month period: 3 weeks starting at the end of march and another 1.5 now.

Overall I am satisfied with this, given the variation in layout involved. Significantly less than an hour per page on average, which is what I was aiming for. For reference, the final pages of tables took about 10 minutes per page to type up, less when there was copy/paste involved.

What took long was of course overhead in setting up macros for some particular structure, and wrestling troff when there was some wrinkle. On the latter, I did like working with troff, but there were a good number of frustrating moments when it behaved differently from what I expected and I had to puzzle out why and/or how to work around it. I got the feeling that there were some leaky abstractions going on and sometimes I just didn't have the full picture of how it actually operated under the hood.

Anyway, still have to make a title page and then I'll have to put the PDF up on the web somewhere, I guess! :)

done! still haven't decided whether to add the "prison bars" or not. but managed to replicate the original's page and line breaks pretty exactly. this needed just a few tweaks here and there.

i had a choice to make here: arrange it so that every item ends up in the same place on the same page as in the original, even if a bunch of it doesn't make any sense?
i decided to do so. the benefit would be that someone familiar with the original table (which i am guessing is a few people), for all its terrible layout, would not be confused by looking at a different table that would still have had pretty bad layout.

so any changes made to the table cannot change the relative positions of things, unless or until i rebuild the whole damn thing as part of a (hypothecial) larger effort.

there are a few errata items that can be fixed without changing the layout. not in this first edition, though. keeping all the typos and stuff, so i can make a clean diff just for them.

#troff #typesetting #c64

not far now, 13 pages to go.

#c64 #troff #typesetting

home stretch!
but ugh, it's >20 pages of this.

#typesetting #c64

Most hilarious #OpenBSD bug I've seen in a while: The kernel can panic when pressing the CapsLock key: https://marc.info/?l=openbsd-bugs&m=178186466408482&w=2

Fortunately, true hackers have mapped CapsLock to Control 

'Panic when pressing Caps Lock in the console' - MARC

i could use feedback on this.

while i reproduce a lot of things in somewhat embarassingly close detail, one thing i am not at all wedded to is the IMHO atrocious typesetting of tables in the original programmer's guide.

i'm confident this one, for instance, does not need internal vertical rules. in fact, no vertical rules at all?

#commodore #c64 #typesetting #retrocomputing

Outstanding article, nice to see #hackers from a different perspective :-)

https://taramariagonzalez.substack.com/p/every-single-outfit-in-hackers

Every Single Outfit in Hackers

If computer nerds wore Vivienne Westwood.

Cult Classic
z386: An Open-Source 80386 Built Around Original Microcode https://nand2mario.github.io/posts/2026/z386/
z386: An Open-Source 80386 Built Around Original Microcode - Small Things Retro