all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: emacs-devel@gnu.org
Subject: Re: standard output/error/input streams
Date: Fri, 20 Jan 2017 13:38:07 +0000	[thread overview]
Message-ID: <878tq5c0n4.fsf@russet.org.uk> (raw)
In-Reply-To: <m21svzzf9f.fsf@newartisans.com> (John Wiegley's message of "Wed,  18 Jan 2017 23:21:32 -0800")

John Wiegley <jwiegley@gmail.com> writes:

>>>>>> "PL" == Phillip Lord <phillip.lord@russet.org.uk> writes:
>
> PL> The main motivation for this is the same as last time; it gives a
> PL> communication channel with Emacs which does not involve buffers at any
> PL> point. Although, if you search for "Emacs" and "standard output", other
> PL> people would like the same thing for other reasons.
>
> Have you thought of allowing files to be "opened" for direct writing as well?
> That is, I'd rather see file handles become a new output stream type, with
> stdout and stderr instances of these, than hard-coded streams for only stdout
> and stderr. Although, getting cleanup right makes me less certain.

Yes, that would be nice I agree, although standard out gives me my main
use case, and there is already support for clean up.

I'll take a look next maybe.

Phil



  reply	other threads:[~2017-01-20 13:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-14 12:22 standard output/error/input streams Phillip Lord
2017-01-14 14:03 ` Noam Postavsky
2017-01-14 14:31 ` Eli Zaretskii
2017-01-14 17:51   ` Eli Zaretskii
2017-01-19  7:21 ` John Wiegley
2017-01-20 13:38   ` Phillip Lord [this message]
2017-01-20 16:26   ` Stefan Monnier
2017-01-20 21:24     ` John Wiegley
2017-01-20 21:52       ` Stefan Monnier
2017-01-20 21:59         ` John Wiegley
2017-01-23 12:41         ` Phillip Lord
2017-01-23 13:11           ` Stefan Monnier

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=878tq5c0n4.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --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 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.