all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Wiegley <jwiegley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, Phillip Lord <phillip.lord@russet.org.uk>
Subject: Re: Adding streams for standard out and standard err
Date: Tue, 02 Aug 2016 16:35:17 -0700	[thread overview]
Message-ID: <m24m72n3re.fsf@newartisans.com> (raw)
In-Reply-To: <83eg6nysug.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 21 Jul 2016 17:21:43 +0300")

>>>>> "EZ" == Eli Zaretskii <eliz@gnu.org> writes:

EZ> Can we take a step back and talk about the need and the use cases?

At least for Eshell, I have wanted the ability to open and read/write directly
to file handles before. The main problem I see is problems such as exhaustion,
since we'd then have another resource being held open and managed by Emacs.
The downsides may not be worth the limited use cases.

-- 
John Wiegley                  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com                          60E1 46C4 BD1A 7AC1 4BA2



  parent reply	other threads:[~2016-08-02 23:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-20 22:48 Adding streams for standard out and standard err Phillip Lord
2016-07-21  7:12 ` Andreas Schwab
2016-07-21 18:42   ` Phillip Lord
2016-07-25  7:35     ` Andreas Schwab
2016-07-21 14:21 ` Eli Zaretskii
2016-07-21 14:40   ` Paul Eggert
2016-07-21 15:02     ` Eli Zaretskii
2016-07-21 19:01       ` Phillip Lord
2016-07-21 18:52   ` Phillip Lord
2016-07-21 19:11     ` Eli Zaretskii
2016-07-21 20:13       ` Phillip Lord
2016-07-22  6:50         ` Eli Zaretskii
2016-07-22 15:43           ` Phillip Lord
2016-07-21 22:15     ` Davis Herring
2016-08-02 23:35   ` John Wiegley [this message]
2016-07-22 14:48 ` Phil Sainty
2016-07-22 15:42   ` Phillip Lord

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=m24m72n3re.fsf@newartisans.com \
    --to=jwiegley@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=phillip.lord@russet.org.uk \
    /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.