Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: 4.3.12-test-2
- X-seq: zsh-workers 29839
- From: Peter Stephenson <Peter.Stephenson@xxxxxxx>
- To: "Zsh Hackers' List" <zsh-workers@xxxxxxx>
- Subject: Re: 4.3.12-test-2
- Date: Fri, 21 Oct 2011 12:08:48 +0100
- In-reply-to: <20111021102007.GB23272@redoubt.spodhuis.org>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- Organization: Cambridge Silicon Radio
- References: <20111020213929.410073fe@pws-pc.ntlworld.com> <20111021102007.GB23272@redoubt.spodhuis.org>
On Fri, 21 Oct 2011 06:20:07 -0400
Phil Pennock <zsh-workers+phil.pennock@xxxxxxxxxxxx> wrote:
> Between 4.3.12 and HEAD/4.3.12-test-2 I've started getting:
>
> /home/phil/.zshenv:133: failed to close file descriptor 1: bad file descriptor
> /home/phil/.zshenv:136: failed to close file descriptor 1: bad file descriptor
> /home/phil/.zshenv:142: failed to close file descriptor 1: bad file descriptor
> /home/phil/.zshenv:146: failed to close file descriptor 1: bad file descriptor
>
> Those correspond to function definitions of the form:
>
> functions >&- have_cmd || function have_cmd { [[ -x =$1 ]] 2>/dev/null }
Hmm... I'm getting an error from closing stdout (just once), too. That
doesn't seem right and needs looking into. Possibly the error is
failing to close it, rather than the new error message (which is
deliberate if the shell fails to do an operation on file descriptors
you've explicitly asked for), so the real problem may not be new.
--
Peter Stephenson <pws@xxxxxxx> Software Engineer
Tel: +44 (0)1223 692070 Cambridge Silicon Radio Limited
Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, UK
Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom
More information can be found at www.csr.com. Follow CSR on Twitter at http://twitter.com/CSR_PLC and read our blog at www.csr.com/blog
Messages sorted by:
Reverse Date,
Date,
Thread,
Author