Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <160105083303.ZM3620@torch.brasslantern.com>
Date: Tue, 5 Jan 2016 08:33:03 -0800
In-Reply-To: <20160105114701.5b7d8363@pwslap01u.europe.root.pri>
Comments: In reply to Peter Stephenson <p.stephenson@samsung.com>
        "Re: PATCH: refactor memstream for "print -v"" (Jan  5, 11:47am)
References: <160104231830.ZM20279@torch.brasslantern.com> 
	<20160105094821.307cca71@pwslap01u.europe.root.pri> 
	<20160105114701.5b7d8363@pwslap01u.europe.root.pri>
To: zsh-workers@zsh.org
Subject: Re: PATCH: refactor memstream for "print -v"
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Jan 5, 11:47am, Peter Stephenson wrote:
} Subject: Re: PATCH: refactor memstream for "print -v"
}
} On Tue, 5 Jan 2016 09:48:21 +0000
} Peter Stephenson <p.stephenson@samsung.com> wrote:
} > > - I note in passing that "print something >&-" is explicitly not an error,
} > >   but "print -u1 something >&-" IS an error.  Also unchanged here.
} > 
} > In the second case we've explicitly been told to "do something" with the
} > fd, which happens to be dup'ing and fdopen'ing it.  There's no such code
} > in the first place, and there doesn't seem any point in making the
} > second case silent.
} 
} Actually, it appears this is deliberate.

Yeah, I knew it was deliberate, though I'd forgotten about the discussion
with Zefram.

Recent bash do emit an error on "echo >&-", for whatever that's worth, in
case we want to revisit Zefram's argument.