From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: Different behaviour of zsh with two input redirections compared to all other POSIX shells I have installed
Date: Mon, 15 Dec 2014 11:46:57 +0000 [thread overview]
Message-ID: <20141215114657.1be3fca4@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <20141215113312.GJ26664@sym.noone.org>
On Mon, 15 Dec 2014 12:33:14 +0100
Axel Beckert <abe@deuxchevaux.org> wrote:
> Is this expected/wanted zsh behaviour? Is this something we should fix
> in zsh? And if so, should it rather behave like bash or like tcsh? :-)
You'll need to try with "unsetopt multios" before comparing with other
shells. (I'm not suggesting that necessarily removes all issues...)
pws
next prev parent reply other threads:[~2014-12-15 11:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 11:33 Axel Beckert
2014-12-15 11:46 ` Peter Stephenson [this message]
2014-12-15 11:53 ` Axel Beckert
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=20141215114657.1be3fca4@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.com \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).