From: phillip.lord@russet.org.uk (Phillip Lord)
To: Andreas Schwab <schwab@suse.de>
Cc: emacs-devel@gnu.org
Subject: Re: Adding streams for standard out and standard err
Date: Thu, 21 Jul 2016 19:42:19 +0100 [thread overview]
Message-ID: <87shv23kac.fsf@russet.org.uk> (raw)
In-Reply-To: <mvmh9bj79dl.fsf@hawking.suse.de> (Andreas Schwab's message of "Thu, 21 Jul 2016 09:12:06 +0200")
Andreas Schwab <schwab@suse.de> writes:
> phillip.lord@russet.org.uk (Phillip Lord) writes:
>
>> +Two functions which are specifically designed for use as output
>> +streams:
>> +
>> +@table @asis
>> +@cindex @code{stdout} output stream
>> +@item @var{stdout}
>> +Prints to the system standard output (as opposed to the
>> +@var{standard-output}), regardless of whether Emacs is running
>> +interactively or not.
>> +
>> +@item @var{stderr} output stream
>> +Prints to the system standard error, regardless of whether Emacs is
>> +running interactively or not.
>> +@end table
>
> That's not a good name for these functions. Since they do the printing
> their name should include `print'.
Yes, this is true, although they only print single characters, which is
pretty useless for most people. In actual use, they look like this:
(print "hello" 'stdout)
Extending the name to reflect the full function:
(print "hello" 'printchar-to-stdout)
Seemed a bit duplicative to me.
Phil
next prev parent reply other threads:[~2016-07-21 18:42 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 [this message]
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
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=87shv23kac.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=emacs-devel@gnu.org \
--cc=schwab@suse.de \
/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.