From: Rich Salz <rsalz@osf.org>
To: arnold@cc.gatech.edu, sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: sam and varios mail programs
Date: Thu, 8 Dec 1994 11:50:24 -0500 [thread overview]
Message-ID: <9412081650.AA06397@sulphur.osf.org> (raw)
I modified sam so that when creating the fifo it first did
getenv("sampipe")
and if that existed it used that as the name of the pipe. I set that
variable in my .rcrc which is sourced by my X startup stuff.
For editing I set VISUAL to $home/bin/callsam, which is this:
#! /bin/rc
~ $#* 1 || {
echo Usage: `{basename $0} file >[1=2]
exit 1
}
~ $#sampipe 0 && {
sampipe=$home/.sam.$USER
! ~ $#DISPLAY 0 && sampipe=$sampipe.$DISPLAY
}
! test -r $sampipe && {
echo `{basename $0} ^ ': No pipe "' ^ $sampipe ^ '" to sam' >[1=2]
exit 1
}
{ switch ($1) {
case /*
echo B $1
case *
echo B `{builtin pwd} ^ / ^ $1
} }>$sampipe
echo Type EOF when done:
cat
# Could use "sed 1q" to get just a newline but I prefer the EOF.
next reply other threads:[~1994-12-08 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-12-08 16:50 Rich Salz [this message]
-- strict thread matches above, loose matches on Subject: below --
1994-12-08 16:56 Arnold Robbins
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=9412081650.AA06397@sulphur.osf.org \
--to=rsalz@osf.org \
--cc=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).