public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Peter A. Castro" <doctor@fruitbat.org>
To: Thomas Hafner <{^_^}@hafner.NL.EU.ORG>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: 1.7.9: zsh, "unexpected end of file"
Date: Tue, 06 Dec 2011 07:13:00 -0000	[thread overview]
Message-ID: <alpine.LNX.2.00.1112052258320.3448@gremlin.fruitbat.org> (raw)
In-Reply-To: <20111130204840.8840E1412D4@faun.hafner.NL.EU.ORG>

On Wed, 30 Nov 2011, Thomas Hafner wrote:

> Hello,

Greetings, Thomas,
   (sorry for the late reply)

> could zsh be repaired such that it behaves successfully like bash?
> Here goes the problem description.
>
> 1. In shell /usr/bin/zsh-4.3.12.exe:
>  gunzip < r1s.gz > r1s
>  - Expected: unpack to r1s
>  - Observed: command fails with output "gzip: stdin: unexpected end of
>    file"
> 2. However this works:
>  gunzip r1s.gz
> 3. If I repeat 1. with bash rather than zsh, it works.
>
> The file r1s.gz can be get there http://tinyurl.com/bs7kefh .

Most curious.
I can repro your symptoms.  However, the following combinations do work:

   cat r1s.gz | gunzip > r1s
   zcat r1s.gz > r1s

It seems only directly re-directing stdin fails.

Hmm...there's something rather strange about this specific .gz file of
yours.  I'll have to analyse it a little more to determine what's going
on.  On a guess, I'd say there's a control sequence in it that's tickling
the I/O handler in some interesting way.

How, exactly, (if I may ask), did you create this file?
It looks like random noise to me.

> Regards
>  Thomas Hafner

-- 
Peter A. Castro <doctor@fruitbat.org> or <Peter.Castro@oracle.com>
 	"Cats are just autistic Dogs" -- Dr. Tony Attwood

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2011-12-06  7:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-30 21:09 Thomas Hafner
2011-12-06  7:13 ` Peter A. Castro [this message]

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=alpine.LNX.2.00.1112052258320.3448@gremlin.fruitbat.org \
    --to=doctor@fruitbat.org \
    --cc=cygwin@cygwin.com \
    --cc={^_^}@hafner.NL.EU.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.
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).