From: Barry Margolin <barmar@genuity.net>
Subject: Re: Piped insert-file?
Date: Thu, 14 Nov 2002 16:52:29 GMT [thread overview]
Message-ID: <hxQA9.12$Xq1.1204@paloalto-snr1.gtei.net> (raw)
In-Reply-To: ar0k64$q5o$1@reader1.panix.com
In article <ar0k64$q5o$1@reader1.panix.com>,
ginak <gina02122000@yahoo.com> wrote:
>Is there a way (without creating a temporary file) to insert into a
>buffer the results of running a file's contents through a Unix pipe?
C-u M-! and C-u M-| will execute commands and insert the output in the
current buffer. The second command pipes the current region to the command
and replaces it with the output.
--
Barry Margolin, barmar@genuity.net
Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.
next prev parent reply other threads:[~2002-11-14 16:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 16:49 Piped insert-file? ginak
2002-11-14 16:52 ` Barry Margolin [this message]
2002-11-14 18:10 ` ginak
2002-11-14 19:10 ` Stefan Monnier <foo@acm.com>
2002-11-14 19:13 ` Barry Margolin
2002-11-14 17:26 ` Friedrich Dominicus
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='hxQA9.12$Xq1.1204@paloalto-snr1.gtei.net' \
--to=barmar@genuity.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).