From: seanq@plan9.bell-labs.com
To: 9fans@cse.psu.edu, sam-fans@hawkwind.utcs.toronto.edu
Date: Tue, 29 Jul 1997 17:25:55 -0400 [thread overview]
Message-ID: <97Jul29.201153edt.24651@hawkwind.utcs.utoronto.ca> (raw)
For those of you that use Sam on Windows 95/NT:
There is a new version which can be installed by running
the self extracting executable available thru netlib.
Go to
http://netlib.bell-labs.com/netlib/research
and select the file sam.exe, or more directly,
http://netlib.bell-labs.com/netlib/research/sam.exe
Major changes from the previous release include:
*) The commands that run external programs now work, i.e. '<', '>', '|', '!'.
Included with the distribution are several command line programs
that are useful with sam, such as: pwd, echo, fmt, and sort.
*) There is a 'B' command that enables sam to receive file open requests
from other programs.
Let me know any problems you have.
seanq@research.bell-labs.com
reply other threads:[~1997-07-30 0:11 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=97Jul29.201153edt.24651@hawkwind.utcs.utoronto.ca \
--to=seanq@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
--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).