X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
        bh=T8xbSEPTTMWehbb1nNHpQ/Nzrvh/mlnSCp69YbcrJs4=;
        b=tjKLS30HrhRRLnI0xAO4H6h8wX1+21aUNPimPJSHfyRizhr/YeonwaHVglo+d9DKFO
         JlW9PiFh+0wXCDV84ZPpTFkk9ldXGQEOHIv4VJVvusAGjapyhI3ZM93JQsK0EiwVNyO0
         5XZffR+PRIv/h6HFuyzSllIBsafCrmaOz7NPj3JsiG+J+qnxbhRxqCZt6KRoRI1b0AjO
         siUNV79/sF4YykoIxxySBoF4vnzyVmPhst9DCfmZtzZ0HlA54XpRfUx65tG4+aiP2zGW
         CliHtyaPKU6D+Z6EdjfNeUaER+TK2chy+VLa2o7QuZ7Zettf7sPL7yO41MDO/9jVzEYZ
         1l7g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:in-reply-to:references:from:date
         :message-id:subject:to;
        bh=T8xbSEPTTMWehbb1nNHpQ/Nzrvh/mlnSCp69YbcrJs4=;
        b=RXX7U/H67qoqOY+vMccmmQAsOIAUMISWg7xY+r3tdgj8OFbxcsJiFzVfr4TfEd3T6w
         LkhiuiU/QQCeoXJMZO+IKNquEQlUnlCfGZvH/PbVc+DhJDY0VMOc58nCceRDXcmX7v2A
         BocTxoydbAGhNshkEkWGq9Fm9muWLxEeGGiMdqHYoBGFLNoo7pfQ4a2o4vN+xMFPrmIT
         ra5i1+kI+Bde9BHZN4ICCrNc2tGG5YiGCHwbPER0RGFdlLaKWt7Nlk+wMMwkKTrsAxJ/
         fOlNvfn+odCvQfTpwbwAaWS5WOjh34o1j148YgLujSP0a99wu8DaZzLA4h4DwKpnovsT
         VhEw==
X-Gm-Message-State: AOAM5310Nw6k3k4k+YRTRz80MiRO8AjAk7Tz+tW72/RgzbW9nleiZTm1
	/7yH5Hbj2nmrh+c2+TsKy/gde6ocqUOEIXkgLRw8H0R+
X-Google-Smtp-Source: ABdhPJxQIm7k3P7ZJ9N2f+9AE638cPPBAWlnvGH7xryTabCP0y33SRvKkiWk/lAnV36wh0QEmSbHAznZFKMT33Ge8i8=
X-Received: by 2002:a9d:5a8d:: with SMTP id w13mr16279879oth.145.1616856711513;
 Sat, 27 Mar 2021 07:51:51 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <83mtuooepe.fsf@gnu.org>
References: <CAA2C=vDMw+wQsbxDkYcXsPgdqeUMDNwz7-NCujx+G11M1vpmzg AT mail DOT gmail DOT com>
 <83o8f4oftm DOT fsf AT gnu DOT org> <CAA2C=vCGH8k2CGEnNXrfZq7CcEExOOrX5TRh0+Kt94f5Oc_g2g AT mail DOT gmail DOT com>
 <83mtuooepe DOT fsf AT gnu DOT org>
From: "Ozkan Sezer (sezeroz AT gmail DOT com) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
Date: Sat, 27 Mar 2021 17:51:51 +0300
Message-ID: <CAA2C=vBVv_XrMWf65b_ou05VEGkghTiG-QPFoZuKxfdv5kjUcw@mail.gmail.com>
Subject: Re: issue with popen and reading from stdout
To: djgpp AT delorie DOT com
Content-Type: text/plain; charset="UTF-8"
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On 3/27/21, Eli Zaretskii (eliz AT gnu DOT org) [via djgpp AT delorie DOT com]
<djgpp AT delorie DOT com> wrote:
>> From: "Ozkan Sezer (sezeroz AT gmail DOT com) [via djgpp AT delorie DOT com]"
>> <djgpp AT delorie DOT com>
>> Date: Sat, 27 Mar 2021 17:18:20 +0300
>>
>> > The above program's expected effect is to read what "unrar -p" emits
>> > without any EOL conversions.  Programs that run on MS-DOS/Windows
>> > usually output CRLF end-of-line sequences (i.e. 0x0d + 0x0a), so the
>> > program you show should:
>> >
>> >  . read these CRLF EOLs without any conversion
>> >  . write each line to stdout
>>
>> OK, so it's possibly an issue with unrar itself
>
> You expected unrar to produce lines with a single 0x0a at the end of
> each line?  That's extremely unusual with DOS/Windows programs.

The archived file is binary not a text, although unrar might have screwed up.

EDIT: For what it's worth, windows version doesn't have the issue.