From: rob@research.att.com
To: sam-fans@hawkwind.utcs.toronto.edu
Date: Sun, 7 Mar 1993 16:05:49 -0500 [thread overview]
Message-ID: <93Mar7.161335est.2782@hawkwind.utcs.toronto.edu> (raw)
it would be nice, you're right. the problem lies in sam's design:
splitting the text between host and terminal makes it a logistical
nightmare to handle the scrolling during selection. it has been
tried but the communications in the middle made it too slow to
install. so engineering, rather than intention, forced the
omission of the feature.
-rob
reply other threads:[~1993-03-07 21:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=93Mar7.161335est.2782@hawkwind.utcs.toronto.edu \
--to=rob@research.att.com \
--cc=sam-fans@hawkwind.utcs.toronto.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).