From: arnold@cc.gatech.edu (Arnold Robbins)
To: sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: sam and varios mail programs
Date: Thu, 8 Dec 1994 11:56:35 -0500 [thread overview]
Message-ID: <199412081656.LAA04852@penfold.cc.gatech.edu> (raw)
In-Reply-To: rob@plan9.research.att.com's 15-line message on Dec 8, 11:48am
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 481 bytes --]
> (various?)
*I* can spell. My keyboard can't, though. ☺
> why not change your EDITOR variable to be a script
> that uses B to get the file into sam,
This is the easy part.
> and some other
> signal or watchdog to get it back?
This is the hard part. It happens that if I do something like this
with mush, and simply wait until I've finished with the editor, I'm ok,
but it's pretty fragile. That's why I was wondering if someone else had
beat me to inventing this wheel.
next reply other threads:[~1994-12-08 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-12-08 16:56 Arnold Robbins [this message]
-- strict thread matches above, loose matches on Subject: below --
1994-12-08 16:50 Rich Salz
1994-12-08 16:35 Arnold Robbins
1994-12-08 7:55 Jonathan Shopiro
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=199412081656.LAA04852@penfold.cc.gatech.edu \
--to=arnold@cc.gatech.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).