all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: Redirecting standard output
Date: Thu, 21 Apr 2011 09:10:59 +0300	[thread overview]
Message-ID: <83oc402ky4.fsf@gnu.org> (raw)
In-Reply-To: <m3hb9sbc8t.fsf@quimbies.gnus.org>

> From: Lars Magne Ingebrigtsen <larsi@gnus.org>
> Date: Thu, 21 Apr 2011 03:54:10 +0200
> 
> Hm...  oh!  process.c isn't compiled at all on MS-DOS?

It is, but only its last part, the one outside the "#ifdef subprocesses"
condition.  Which doesn't include start-process and its subroutines,
of course.

And I'm not sure this is the only reason why we have 2 APIs instead of
one.

> Hm.  Shame.  It would have been nice if those two (very similar
> functionality-wise) functions could have been merged somehow...

If you do it, I promise to review the patches and test them.  I myself
don't plan investing such a serious effort in such a central part of
Emacs any time soon.  I think you greatly underestimate the effort
needed here; the amount of #ifdef's in call-process should tell you
something.  (There were much more of these #ifdef's originally, but
Dan's efforts brought them to the current state, which is probably the
absolute minimum.)  Making start-process compile on MS-DOS will need
to introduce an even larger amount of #ifdef's into it, which is
hardly a step into the right direction.

And anyway, I'm not sure your conclusion about these 2 APIs being very
similar is indeed true.  Nor do I see how start-process solves your
problem: it doesn't let you separate stdout and stderr at all, unless
you go through a shell.  What am I missing?



  reply	other threads:[~2011-04-21  6:10 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
2011-04-21  6:10     ` Eli Zaretskii [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83oc402ky4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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.