From: phillip.lord@russet.org.uk (Phillip Lord)
To: Eli Zaretskii <eliz@gnu.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>, emacs-devel@gnu.org
Subject: Re: Adding streams for standard out and standard err
Date: Thu, 21 Jul 2016 20:01:19 +0100 [thread overview]
Message-ID: <87fur23jeo.fsf@russet.org.uk> (raw)
In-Reply-To: <83vazzxce3.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 21 Jul 2016 18:02:28 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Cc: emacs-devel@gnu.org
>> From: Paul Eggert <eggert@cs.ucla.edu>
>> Date: Thu, 21 Jul 2016 16:40:10 +0200
>>
>> On 07/21/2016 04:21 PM, Eli Zaretskii wrote:
>> > . We already have (append-to-file START END FILENAME), which can be
>> > used to write a buffer or a string to a file. FILENAME can be
>> > "/dev/stderr" on Posix platforms, for example, or it can be a real
>> > file name.
>>
>> Wouldn't the proposed primitives often be more efficient than
>> append-to-file, since they would use stdio buffering?
>
> Probably. But is performance relevant to the use cases we intend them
> to be used?
You are correct in this case, performance is irrelevant. In fact,
buffering is a bit of a pain. It took me a few minutes to work out why
(print "hello" 'stdout)
worked but
(princ "hello" 'stdout)
didn't -- the latter gets buffered.
>> Presumably people using the new primitives would know about their
>> problems with tty and/or GUI frames, just as they know about the similar
>> problems that append-to-file has with /dev/stderr.
>
> I'm not so sure. But that's not the important part of my reasoning.
It's important to the "unreliable/dangerous" part of your argument.
I will add further documentation to the patch, pointing out this
potential problem.
Phil
next prev parent reply other threads:[~2016-07-21 19:01 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 [this message]
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
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=87fur23jeo.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=eggert@cs.ucla.edu \
--cc=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 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.