From: Scott Schwartz <schwartz@groucho.cs.psu.edu>
To: Sam Fans <sam-fans@hawkwind.utcs.toronto.edu>
Subject: send
Date: Thu, 3 Dec 1992 21:41:34 -0500 [thread overview]
Message-ID: <92Dec3.214153est.2516@groucho.cs.psu.edu> (raw)
Picture this. In one buffer you have some text, which is selected as
dot. In the sam window you have some stuff, including ``|fmt''. In
the sam window, you sweep out ``|fmt'' and select "send" twice in a
row. The second time, the command fails, because the output of the
pipe has become the text to send. Does anyone else find that odd?
next reply other threads:[~1992-12-04 2:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-12-04 2:41 Scott Schwartz [this message]
1992-12-04 2:47 ` send Chris Siebenmann
1992-12-04 7:03 ` send John Mackin
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=92Dec3.214153est.2516@groucho.cs.psu.edu \
--to=schwartz@groucho.cs.psu.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).