From: gregoryj@hotpop.com (Gregory J.)
Subject: Opening stdin or pipe
Date: 24 Feb 2003 21:43:08 -0800 [thread overview]
Message-ID: <eb7f096.0302242143.5bc145d2@posting.google.com> (raw)
I want to be able to pipe data into an Emacs buffer (a new one in a
new Emacs session would be fine). Preferably, I'd use a normal shell
pipeline something like this:
whatever-command | emacs -
I'd be happy enough to use a named pipe like this, though:
mkfifo myfifo
whatever-command > myfifo &
emacs myfifo
It seems the first method is simply not supported (Error: "Option `-'
is ambiguous"). I would have expected the second method to work, but I
get this error: "File exists but cannot be read."
I searched the USENET archive and found this command suggested:
emacs /dev/stdin
(and /dev/stdin does exist under NetBSD), but I get the same error,
"File exists but cannot be read."
A workaround is to run:
mkfifo myfifo
whatever-command > myfifo &
emacs
and then within Emacs create a buffer and run "cat myfifo" via
shell-command (C-u M-!), but this is inconvenient.
Is there any way to accomplish what I described?
next reply other threads:[~2003-02-25 5:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 5:43 Gregory J. [this message]
2003-02-25 8:03 ` Opening stdin or pipe Kai Großjohann
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=eb7f096.0302242143.5bc145d2@posting.google.com \
--to=gregoryj@hotpop.com \
/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).