From: hc05@summitis.com
To: sam-fans@hawkwind.utcs.toronto.edu (Sam mailing list)
Subject: sam pipes
Date: Thu, 20 Apr 1995 15:41:51 -0400 [thread overview]
Message-ID: <9504201938.AA19245@cheetah> (raw)
Forwarded message:
>Does anyone actually use sam's input pipe, apart from with
>the B command? Generally, I've hardly used it at all, but I
>was reading Rob's Acme paper the other day, and it mentioned
>sam interacting with the compiler and debugger, and I thought,
>why not?
I've used it to add a menu to sam that contains some common command sequences
I use, like shifting left, or running text through a spell checker. None
of it is especially tricky, but it helps me keep my hands off of the keyboard.
I basically get the pipe name and build a 9menu.
I like your script. I'll have to get rc, or rewrite it in perl.
Beirne
--
-------------------------------------------------------------------------------
Beirne Konarski | Reading maketh a full man, conference a
beirnek@summitis.com | ready man, and writing an exact man.
"Untouched by Scandal" | -- Francis Bacon
-------------------------------------------------------------------------------
reply other threads:[~1995-04-20 19:42 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=9504201938.AA19245@cheetah \
--to=hc05@summitis.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).