The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Adam Thornton <>
To: Jim Geist <>
Cc: The Eunuchs Hysterical Society <>
Subject: [TUHS] Re: Emacs on v7
Date: Thu, 24 Aug 2023 20:02:59 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1462 bytes --]

LCML is not open to physical visitors but a couple days ago, someone posted
on Mastodon about misspiggy and you can ssh and it works, so....

On Thu, Aug 24, 2023 at 5:19 PM Jim Geist <> wrote:

> misspiggy? Is LCML back open?
> On Thu, Aug 24, 2023 at 5:26 PM Adam Thornton <> wrote:
>> I finally got an Emacs running on v7--it's on misspiggy at LCML now as
>> "ue".
>> It's Microemacs 3.6; what I did was to clone
>> and check out the first commit.
>> Some experimentation later, it had the usual problem with v7 and DEC
>> linkers that not all the function names (er, more generally exported
>> symbols, but in this case, function names) were unique in the first 7
>> characters (which is 6 if you're working with DEC OSes).  So a bit of sed
>> later and I had something that built, linked, and appears to run with
>> TERM=vt100 set.
>> Arrow keys, naturally, don't work, but C-b, C-f, C-p, C-n do.
>> I think I'm going to just make a GH repo of it, but I'm happy to send the
>> tarball, or tar.uue, upon request.  I find UUCP kinda fragile on my simh
>> installation, and I don't know how to get to Miss Piggy's (although the
>> uucp commands are there), so, well, uuencoding, a pasteboard buffer,
>> iTerm2's "Paste Slowly", and cat will work as a file transfer mechanism.
>> Adam

[-- Attachment #2: Type: text/html, Size: 2262 bytes --]

  reply	other threads:[~2023-08-25  3:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24 23:26 [TUHS] " Adam Thornton
2023-08-25  0:19 ` [TUHS] " Jim Geist
2023-08-25  3:02   ` Adam Thornton [this message]
2023-08-25  5:53     ` Lars Brinkhoff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).