From: erik quanstrom <quanstro@Infomkt.ibm.com>
To: sam-fans@hawkwind.utcs.toronto.edu
Subject: re: sam for 95/nt
Date: Mon, 17 Feb 1997 12:01:05 -0500 [thread overview]
Message-ID: <199702171701.MAA106172@dingler.dev.infomkt.ibm.com> (raw)
>(I haven't figured out how to type a CR, and just copy them from other text files).
<compose> X000d
where <compose> is usually the <alt> key. i don't know if this works on the win{nt,95}
version
next reply other threads:[~1997-02-17 17:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-02-17 17:01 erik quanstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-02-18 4:02 arnold
1997-02-17 17:15 Pete Fenelon
1997-02-17 16:54 rsc
1997-02-17 16:35 Nigel Roles
1997-02-17 16:26 Pete Fenelon
1997-11-17 15:58 ` Michael K. Rosenberg
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=199702171701.MAA106172@dingler.dev.infomkt.ibm.com \
--to=quanstro@infomkt.ibm.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).