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, 08 Feb 2013 10:40:22 +0200 [thread overview]
Message-ID: <83fw178ah5.fsf@gnu.org> (raw)
In-Reply-To: <87txpnpwqb.fsf@servo.finestructure.net>
> From: Jameson Graef Rollins <jrollins@finestructure.net>
> Date: Thu, 07 Feb 2013 14:47:40 -0800
> Cc: 7842@debbugs.gnu.org
>
> Yes, but that requires writing to a temporary file. Avoiding that was
> the entire point of my feature request.
Why do you want to avoid it? What is the problem with using this
method?
> Is there some technical reason that it's impossible to just capture
> the stderr to a separate buffer?
It's possible, but it will complicate the API which is already quite
complicated and hard to maintain for every platform Emacs supports.
next prev parent reply other threads:[~2013-02-08 8:40 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 [this message]
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
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=83fw178ah5.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.