From: David Kastrup <dak@gnu.org>
Subject: Proposal for extending set-process-filter
Date: 27 Apr 2004 01:55:46 +0200 [thread overview]
Message-ID: <x5r7uacn0d.fsf@lola.goethe.zz> (raw)
Currently, processes called with call-process can't have their stdout
and stderr directed to different buffers/filter functions/whatever.
This is painfully obvious when using pipes and redirections in eshell.
I'd propose that set-process-filter gets extended in the following
way:
set-process-filter is a built-in function in `src/process.c'.
(set-process-filter PROCESS FILTER)
Give PROCESS the filter function FILTER; nil means no filter.
t means stop accepting output from the process.
A filter can be
1) a function which gets two arguments. [insert old description]
2) a buffer into which output gets inserted.
3) a file name for output.
4) t to stop accepting output.
5) a list of filter/file descriptor associations.
The car's of the elements of this list are an item from 1)-4) as
above, while the cdr is a list of file ids for which this item is
supposed to apply.
So to redirect output of stdout and stderr to /dev/null, you'd specify
(set-process-filter my-process '(("/dev/null" 1 2)))
If a list is specified in this manner, the operation of unspecified
file descriptors is not affected.
This does not yet do everything needed for a full-bodied eshell: input
redirections (including procedural input, equivalents to filter
functions) and output appending redirection (>>) are not covered
yet. But it would be a first step.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next reply other threads:[~2004-04-26 23:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 23:55 David Kastrup [this message]
2004-04-27 15:01 ` Proposal for extending set-process-filter Stefan Monnier
2004-04-27 15:33 ` David Kastrup
2004-04-27 18:51 ` Stefan Monnier
2004-04-27 20:46 ` David Kastrup
2004-04-27 16:30 ` Richard Stallman
2004-04-27 18:53 ` Stefan Monnier
2004-04-27 20:59 ` David Kastrup
2004-04-29 10:44 ` Richard Stallman
2004-04-27 21:10 ` David Kastrup
2004-04-27 21:25 ` Stefan Monnier
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=x5r7uacn0d.fsf@lola.goethe.zz \
--to=dak@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.