From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: emacs-devel@gnu.org
Subject: Re: Redirecting standard output
Date: Thu, 21 Apr 2011 03:54:10 +0200 [thread overview]
Message-ID: <m3hb9sbc8t.fsf@quimbies.gnus.org> (raw)
In-Reply-To: jwvy634mt5l.fsf-monnier+emacs@gnu.org
I've started reading the code, and it doesn't look too harrowing to
do -- there's a possibility it might make the code simpler, because we'd
basically be able to factor out stdout/stderr handling into one helper
function instead of special-casing the stdout/stderr handling. I think.
But looking at the code, I remembered `start-process', which doesn't
allow separating stderr at all, so I took a look at that function, too.
It's much simpler and cleaner than `call-process'. `call-process' has a
fair bit of #ifdef for DOS and NT and Windows, while `start-process'
doesn't. And even stranger is that if you give a 0 as the value for
`call-process', you get asynchronous behaviour, which is very much like
the behaviour that `start-process' provides. (But without the
possibility of adding filters.)
So here's my question: What's the reason that `call-process' isn't just
a shim around `start-process'?
Hm... oh! process.c isn't compiled at all on MS-DOS? Hm. Shame. It
would have been nice if those two (very similar functionality-wise)
functions could have been merged somehow...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-04-21 1:54 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 21:19 Redirecting standard output Lars Magne Ingebrigtsen
2011-04-20 22:54 ` Stefan Monnier
2011-04-21 1:54 ` Lars Magne Ingebrigtsen [this message]
2011-04-21 6:10 ` Eli Zaretskii
2011-04-21 11:45 ` Lars Magne Ingebrigtsen
2011-04-21 13:25 ` Lars Magne Ingebrigtsen
2011-04-21 14:10 ` Eli Zaretskii
2011-04-21 15:15 ` Lars Magne Ingebrigtsen
2011-04-21 15:46 ` Lars Magne Ingebrigtsen
2011-04-21 16:15 ` Eli Zaretskii
2011-04-21 16:22 ` Lars Magne Ingebrigtsen
2011-04-21 16:24 ` Lars Magne Ingebrigtsen
2011-04-21 16:55 ` Eli Zaretskii
2011-04-21 17:05 ` Jan Djärv
2011-04-21 19:15 ` Eli Zaretskii
2011-04-21 19:19 ` Davis Herring
2011-04-21 19:31 ` Lars Magne Ingebrigtsen
2011-04-22 5:50 ` Eli Zaretskii
2011-04-23 18:46 ` Lars Magne Ingebrigtsen
2011-04-23 20:10 ` Eli Zaretskii
2011-04-24 8:30 ` Jan Djärv
2011-04-30 23:58 ` Lars Magne Ingebrigtsen
2011-05-01 0:06 ` Lars Magne Ingebrigtsen
2011-05-01 17:56 ` Andy Moreton
2011-05-07 11:34 ` Eli Zaretskii
2011-05-07 12:10 ` Eli Zaretskii
2011-05-30 17:39 ` Lars Magne Ingebrigtsen
2011-04-21 16:29 ` Glenn Morris
2011-04-21 8:27 ` Michael Albinus
2011-04-21 5:57 ` Eli Zaretskii
2011-04-21 6:28 ` Thierry Volpiatto
2011-04-21 6:41 ` Eli Zaretskii
2011-04-21 7:33 ` Thierry Volpiatto
2011-04-21 11:40 ` Lars Magne Ingebrigtsen
2011-04-21 11:58 ` Eli Zaretskii
2011-04-21 12:24 ` Lars Magne Ingebrigtsen
2011-04-21 14:25 ` Lars Magne Ingebrigtsen
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=m3hb9sbc8t.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).