From: Charles Forsyth <charles.forsyth@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] A few questions about sam
Date: Thu, 22 Jul 2021 20:24:59 +0100 [thread overview]
Message-ID: <CAOw7k5imOXbgt=7PyFVinmbSRxvtNRwCgXnjbzQ-KbGd8AFDdg@mail.gmail.com> (raw)
In-Reply-To: <16269611020.38ad.33188@composer.9fans.topicbox.com>
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]
>
>
> - The sam tutorial speaks of sam being "downloaded". (*A tutorial for
> the sam language*.) I am not exactly sure what "downloaded" means in
> this context.
>
> sam originally ran on a terminal that had its own little operating system
and applications could be downloaded into each terminal window.
sam ran in two parts: sam on the host and samterm (downloaded) on the
terminal. they communicate using a unique protocol.
Here's a video about the original Blit terminal and how that works:
https://www.youtube.com/watch?v=emh22gT5e9k
(The original editor on the Blit was jim.)
sam is described in detail in a paper:
https://docs.google.com/viewer?url=https%3A%2F%2F9p.io%2Fsys%2Fdoc%2Fsam%2Fsam.pdf
Permalink
> <https://9fans.topicbox.com/groups/9fans/T60b5c1929a63b077-Mf1461873910abb65e9700e7e>
>
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T60b5c1929a63b077-M20b73a1d7ea627a04a463cef
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 2039 bytes --]
next prev parent reply other threads:[~2021-07-22 19:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 13:38 revcomninos
2021-07-22 13:57 ` Sigrid Solveig Haflínudóttir
2021-07-22 14:59 ` revcomninos
2021-07-22 19:10 ` mcz
2021-07-22 19:18 ` Charles Forsyth
2021-07-22 19:24 ` Charles Forsyth [this message]
2021-07-22 20:18 ` revcomninos
2021-07-22 23:45 ` Silas McCroskey
2021-07-23 4:47 ` revcomninos
2021-07-23 5:42 ` Silas McCroskey
2021-07-23 9:53 ` revcomninos
2021-07-27 0:56 ` Ethan Gardener
2021-07-27 6:34 ` revcomninos
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOw7k5imOXbgt=7PyFVinmbSRxvtNRwCgXnjbzQ-KbGd8AFDdg@mail.gmail.com' \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).