all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jameson Graef Rollins <jrollins@finestructure.net>
Cc: 7842@debbugs.gnu.org
Subject: bug#7842: acknowledged by developer (control message for bug 7842)
Date: Fri, 22 Feb 2013 20:23:57 +0200	[thread overview]
Message-ID: <834nh4mcle.fsf@gnu.org> (raw)
In-Reply-To: <87ppzsgu08.fsf@servo.finestructure.net>

> From: Jameson Graef Rollins <jrollins@finestructure.net>
> Cc: rgm@gnu.org, 7842@debbugs.gnu.org
> Date: Fri, 22 Feb 2013 09:04:23 -0800
> 
> >      It is impossible to separate the standard output and standard error
> >   streams of the subprocess, because Emacs normally spawns the subprocess
> >   inside a pseudo-TTY, and a pseudo-TTY has only one output channel.  If
> >   you want to keep the output to those streams separate, you should
> >   redirect one of them to a file--for example, by using an appropriate
> >   shell command.
> 
> I don't believe this at all.

Which part?

> Obviously the command can separate stdout From stderr or it wouldn't
> be able to capture stdout to a buffer and separately redirect stderr
> to a file.

The text above says that it is impossible to separate them without
going through files.  In a pipe, there's only one channel, so you can
either have stderr redirected to the same place as stdout (in which
case they are not separated), or put one of them on a file.  And you
clearly said you don;t want any files.

> Come on, guys.  Let's have a serious discussion here.  No more smoke
> blowing.

I don't know whether anybody is blowing smoke here, but I'm certainly
not doing that.





      reply	other threads:[~2013-02-22 18:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1U3Xsb-00055Y-Le@fencepost.gnu.org>
2011-01-14  2:56 ` bug#7842: 23.2; call-process should be able to send stderr to buffer object Jameson Rollins
2011-01-14  3:56   ` Glenn Morris
     [not found]   ` <handler.7842.C.136026813810926.notifdonectrl.0@debbugs.gnu.org>
2013-02-07 22:38     ` bug#7842: acknowledged by developer (control message for bug 7842) Jameson Graef Rollins
2013-02-07 22:41       ` Glenn Morris
2013-02-07 22:47         ` Jameson Graef Rollins
2013-02-08  8:40           ` Eli Zaretskii
2013-02-13 18:51             ` Jameson Graef Rollins
2013-02-13 21:50               ` Eli Zaretskii
2013-02-22  1:50                 ` Jameson Graef Rollins
2013-02-22  8:46                   ` Eli Zaretskii
2013-02-22 14:17                     ` Stefan Monnier
2013-02-22 14:55                       ` Eli Zaretskii
2013-02-22 17:25                         ` Stefan Monnier
2013-02-22 18:21                           ` Eli Zaretskii
2013-02-22 18:44                           ` Jameson Graef Rollins
2013-02-22 17:08                       ` Jameson Graef Rollins
2013-02-22 17:04                     ` Jameson Graef Rollins
2013-02-22 18:23                       ` Eli Zaretskii [this message]

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=834nh4mcle.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=7842@debbugs.gnu.org \
    --cc=jrollins@finestructure.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.
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.