unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 7842@debbugs.gnu.org, jrollins@finestructure.net
Subject: bug#7842: acknowledged by developer (control message for bug 7842)
Date: Fri, 22 Feb 2013 20:21:15 +0200	[thread overview]
Message-ID: <83621kmcpw.fsf@gnu.org> (raw)
In-Reply-To: <jwvwqu0xo2d.fsf-monnier+emacs@gnu.org>

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: jrollins@finestructure.net,  7842@debbugs.gnu.org
> Date: Fri, 22 Feb 2013 12:25:22 -0500
> 
> >> and already separates stdout from stderr.
> > stderr is put on a file when separated.
> 
> Still, it disproves the statement that "It is impossible to separate the
> standard output and standard error streams of the subprocess".

The statement is that it is impossible to do that without involving
files.

> > The OP seems to object to a solution that would use files, or else he
> > would have used make-temp-file himself.
> 
> He mentions 4 problems with the current situation:
> 
> > * The first touches the disk, the second does not.
> 
> Providing a wrapper that does make-temp-file doesn't solve this point,
> indeed.
> 
> > * The first requires me to pick a temporary file name that does not
> >   collide with an existing file on disk, the second does not.
> > * The first requires me to cleanup a temporary file, the second does
> >   not.
> > * The first is 45 characters long, the second is 13.
> 
> But the wrapper would solve all those 3 remaining points (because the
> wrapper would pay this cost, not Jameson).

Again, the example in
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=7842#33 explicitly
rejects use of any temporary files altogether.

If the Jameson would like to rephrase his position, I'm all ears.





  reply	other threads:[~2013-02-22 18:21 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 [this message]
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

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=83621kmcpw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=7842@debbugs.gnu.org \
    --cc=jrollins@finestructure.net \
    --cc=monnier@iro.umontreal.ca \
    /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).