From: "rob pike, esq." <r@geekmail.cc>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Sam's protocol description?
Date: Fri, 9 Jan 2004 15:58:27 -0800 [thread overview]
Message-ID: <bc7e374a94620ed42e297937f69be33c@google.com> (raw)
In-Reply-To: <200401092331.i09NVC1W012380@adat.davidashen.net>
i don't know of a formal description. the comments in mesg.h (i think)
explain the trickiest part. the rest is just a thicket of application-specific
ad hoc details. nothing thrilling, nothing very clean. it's the worst part
of the program.
but since you mention sam....
i'm sitting in new york this week, working on a server in california using
sam -r and it's just great. sam was written in a 1200 baud age, sam -r
created for the cray (!), and yet it's the most responsive editor around if
there are a few thousand clicks between your terminal and your computer
(pardon me, your desktop and your server).
i never would have expected it to matter for so long.
-rob
next prev parent reply other threads:[~2004-01-09 23:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 23:31 David Tolpin
2004-01-09 23:58 ` rob pike, esq. [this message]
2004-01-10 0:01 ` David Tolpin
2004-01-10 0:21 ` Scott Schwartz
2004-01-10 7:01 ` Rob Pike
2004-01-10 15:46 ` [9fans] acme vdharani
2004-01-10 16:07 ` rob pike, esq.
2004-01-10 13:01 ` [9fans] Sam's protocol description? David Tolpin
2004-01-10 23:15 ` boyd, rounin
2004-01-10 13:31 ` David Tolpin
2004-01-10 23:44 ` boyd, rounin
2004-01-10 13:53 ` David Tolpin
2004-01-11 0:11 ` boyd, rounin
2004-01-10 14:20 ` David Tolpin
2004-01-11 0:27 ` boyd, rounin
2004-01-10 15:54 ` boyd, rounin
2004-01-10 6:44 ` Scott Schwartz
2004-01-10 16:54 ` boyd, rounin
2004-01-10 6:49 ` Lucio De Re
2004-01-10 6:59 ` Rob Pike
2004-01-10 17:03 ` boyd, rounin
2004-01-10 16:07 ` rob pike, esq.
2004-01-10 2:30 ddj
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=bc7e374a94620ed42e297937f69be33c@google.com \
--to=r@geekmail.cc \
--cc=9fans@cse.psu.edu \
/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).