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=5qTsjfP35buaZYrF1RxgnXZ1L5Hv/Gk3lAiWAGaad9U=;
        b=YmZ16tmT2jZNx6XRZ0mEy4pse34y0H0ODaJ2x8bgHUHNTsb6/HDgjqYxe6+jRLy4Ub
         AVT/HELxXMiG9RURbLsXWjphU0mIiOFSFfv9JhTHL/t8Lk/aYqq1JDsebYM69SWV4H//
         PuhvAFVeILafPmbb3zFgulHUrNTzSYV9JJG0OyUkvU6HqxM6kRc+2cP1A8JzAHtCm5L3
         HJyOoREN422zvStDFxmT+uLrOLXPsem0dMhvVmgfM3+Wr3MYPre1HzZYua7/w+bDCWip
         Y6jecoCy1j2oiNADqkLNmdN2dMjMLx3ijaksaGAP8HnwE8z988fGNJDPStVzzkYLTA76
         BwOg==
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=5qTsjfP35buaZYrF1RxgnXZ1L5Hv/Gk3lAiWAGaad9U=;
        b=jbSh25Xvgunq5hZmAiTb6KCbciIh9tG5olvU2ta9ycz4ll7wHnbG4mMRnqLzim9qsa
         TZArutIwu9OhX08kzeQm4SF3mYZhNYNwDWjZVI7WUdk8s1DNlWXBPJn4mubmo+Z1HwlT
         k+q3TTHyUG9XGzz480lwbupUrDXuFZunIVk107tISTXMLwG3BL6AInSbUq8HdPmMeVwY
         BbKYWSev6PL8Imu51b77Ex4Z7y6eZg63g5gNRWjii6JmVklIyCWkacEL6P4UGPaN2Ozw
         6DJ2MKpWgFl5FINBDk6fU4vkzcJtRMc5iCi0nW3xtrF8TI0+yFw0Lr/ERUbfEsthahXW
         dXag==
X-Gm-Message-State: AOAM533xDw1r/VjJSwtiuM7QstBvCM7r5y+R1PH/SFriTPzUZ7qflTH9
	MwGoZ43Jag2EH8bjX6ysxf1Q0WgLDVrye+peLyXRqVXR
X-Google-Smtp-Source: ABdhPJwJ3colNtRLIyZCop5V1GI9+/yxW43ApqmbEbiWO1UXHH+ZEQmNlQ7DgTLK4wyl6EYqWIk781Zzg09tMDmKnXo=
X-Received: by 2002:aca:d4d1:: with SMTP id l200mr13525419oig.119.1616856505761;
 Sat, 27 Mar 2021 07:48:25 -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:48:25 +0300
Message-ID: <CAA2C=vD5-Vy51OX+zq8pxrNnL5NCBk4qKq7812v_nsnbG0iHSA@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.