unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Redirecting standard output
Date: Fri, 22 Apr 2011 01:50:47 -0400	[thread overview]
Message-ID: <E1QD9GR-0006Vv-OE@fencepost.gnu.org> (raw)
In-Reply-To: <m3ipu7l7td.fsf@quimbies.gnus.org> (message from Lars Magne Ingebrigtsen on Thu, 21 Apr 2011 21:31:58 +0200)

> From: Lars Magne Ingebrigtsen <larsi@gnus.org>
> Date: Thu, 21 Apr 2011 21:31:58 +0200
> 
> Davis Herring <herring@lanl.gov> writes:
> 
> > You can call `pipe' more than once; the trouble comes when you have to
> > choose which one to read from to avoid blocking the process.  Probably
> > it's just that no one has bothered to implement it carefully enough with
> > `select' or so.
> 
> Oh, I see...  I was a bit confused about how pipe worked.  Yes, that
> makes sense.  Just hook up the STDERR endpoint to a pipe, too, and
> you're in business.
> 
> For the MSDOS case (with STDERR-to-buffer), we'd just have to open
> another temp file, just like we do with STDOUT, so that's a very minor
> change.
> 
> For the non-MSDOS case, using two pipes and select shouldn't be too
> difficult to implement, I think?

You are in danger of reinventing the wait_reading_process_output
wheel.  I'm not sure that kind of complexity is justified for such a
marginal need, just for the sake of theoretical completeness and/or
symmetry between stdout and stderr.  I think redirecting to a
temporary file and then reading from there is more than adequate, and
all but indistinguishable from the user POV (since we wait for the
process to exit anyway).

> Or are there gotchas when using select in Emacs?

wait_reading_process_output already uses select, so adding another one
is probably not a good idea.



  reply	other threads:[~2011-04-22  5:50 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
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 [this message]
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=E1QD9GR-0006Vv-OE@fencepost.gnu.org \
    --to=eliz@gnu.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).