From: KO Myung-Hun <komh78@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: bug-gnulib@gnu.org
Subject: Re: [PATCH] binary-io: do not treat set_binary_mode() on stdin/out/err as an error on OS/2
Date: Sat, 25 May 2019 12:29:29 +0900 [thread overview]
Message-ID: <5CE8B699.3090908@gmail.com> (raw)
In-Reply-To: <3639ab4a-d9c2-b239-906d-9f9ac2fa8601@cs.ucla.edu>
Hi/2.
Paul Eggert wrote:
> On 5/24/19 4:31 AM, KO Myung-Hun wrote:
>> Setting stdin/out/err to binary mode is allowed on OS/2. But it's not
>> useful, because it generates stair-output hard to read.
>>
>> Instead, let's set them to text mode all the time.
>
> First, that patch doesn't set them to text mode all the time; it does so
> only if isatty returns nonzero.
>
them = stdin/out/err = tty
Therefore, they are always set to text mode whenever set_binary_mode()
is called.
> Second, __gl_setmode_check already has the isatty test, so why do it twice?
>
First setmode() on tty on OS/2 is not error. However,
__gl_setmode_check() always return -1 if tty.
Second, I'm not sure it's guaranteed that __gl_setmode_check() is
equivalent to isatty().
--
KO Myung-Hun
Using Mozilla SeaMonkey 2.7.2
Under OS/2 Warp 4 for Korean with FixPak #15
In VirtualBox v4.1.32 on Intel Core i7-3615QM 2.30GHz with 8GB RAM
Korean OS/2 User Community : http://www.os2.kr/
next prev parent reply other threads:[~2019-05-25 3:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 11:31 [PATCH] binary-io: do not treat set_binary_mode() on stdin/out/err as an error on OS/2 KO Myung-Hun
2019-05-24 20:20 ` Paul Eggert
2019-05-25 3:29 ` KO Myung-Hun [this message]
2019-05-25 13:41 ` Bruno Haible
2019-05-25 14:18 ` KO Myung-Hun
2019-05-25 16:31 ` Bruno Haible
2019-05-25 17:14 ` Paul Eggert
2019-05-26 1:48 ` KO Myung-Hun
2019-05-29 0:47 ` Bruno Haible
2019-05-29 13:32 ` KO Myung-Hun
2019-05-30 0:05 ` Paul Eggert
2019-05-30 0:55 ` Bruno Haible
2019-06-02 6:03 ` Paul Eggert
2019-06-02 9:31 ` Bruno Haible
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5CE8B699.3090908@gmail.com \
--to=komh78@gmail.com \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).