From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5585 invoked by alias); 30 Aug 2014 22:34:11 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 33073 Received: (qmail 14232 invoked from network); 30 Aug 2014 22:34:10 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 From: Bart Schaefer Message-id: <140830153425.ZM29241@torch.brasslantern.com> Date: Sat, 30 Aug 2014 15:34:25 -0700 In-reply-to: <140830150813.ZM28921@torch.brasslantern.com> Comments: In reply to Bart Schaefer "Getting unexpected error from piping "read -d"" (Aug 30, 3:08pm) References: <140830150813.ZM28921@torch.brasslantern.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: Getting unexpected error from piping "read -d" MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Aug 30, 3:08pm, Bart Schaefer wrote: } } torch% read -d '' | head } zsh: bad tcgets: bad file descriptor } } GDB trace from the current source is appended. That stack trace is wrong. Please ignore it; sorry.