From: arnold@cc.gatech.edu (Arnold Robbins)
To: sam-fans@hawkwind.utcs.toronto.edu
Subject: sam and varios mail programs
Date: Thu, 8 Dec 1994 11:35:37 -0500 [thread overview]
Message-ID: <199412081635.LAA04772@penfold.cc.gatech.edu> (raw)
Greetings. I use 'mush' as my mail program, and I have my EDITOR environment
variable set to use sam. The problem comes when I have a sam running, and
then I go to read mail. When I edit my file, it cranks up another sam. But
when that sam quits, it removes the fifo in /tmp that the `B' command uses.
At that point, I can no longer use `B' to communicate with my orignal sam.
My question is, how do *you* handle this? Does anyone have a shell script
that runs B on their temporary mail file such that things stay in sync
after the file is written back out with sam?
(This has probably been discussed before...)
Thanks!
Arnold
next reply other threads:[~1994-12-08 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-12-08 16:35 Arnold Robbins [this message]
-- strict thread matches above, loose matches on Subject: below --
1994-12-08 16:56 Arnold Robbins
1994-12-08 16:50 Rich Salz
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=199412081635.LAA04772@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).