From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Cc: Jett Husher <jetthusher@pm.me>
Subject: Re: Possibly missing explanation on difference between '&>' and '> word 2>&1' with multios in manual
Date: Thu, 21 Oct 2021 14:49:26 +0000 [thread overview]
Message-ID: <20211021144926.GF16034@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <CAH+w=7aJhoaCbpqMiUbKGCgC7aUFbJtkJeqJnBq9JJN9w4Rx5A@mail.gmail.com>
Bart Schaefer wrote on Tue, Oct 19, 2021 at 14:53:50 -0700:
> On Tue, Oct 19, 2021 at 8:25 AM Jett Husher <jetthusher@pm.me> wrote:
> >
> > Did I miss something or is the explanation really not present?
>
> It's not precisely missing, it's just implicit. Excerpts:
>
> "Note that the shell opens all the files to be used in the multio process
> immediately, not at the point they are about to be written."
>
> "Note also that redirections are always expanded in order. This happens
> regardless of the setting of the MULTIOS option, but with the option in
> effect there are additional consequences."
>
> It's not that "&>word" all by itself is not the same as ">word 2>&1"
> alone, it's that "&>word" when combined with other redirections is not
> the same as ">word 2>&1" combined with other redirections.
So, s/not have the same effect as/not equivalent to/?
(regex to be applied to the docs sentence Jett quoted)
Cheers,
Daniel
next prev parent reply other threads:[~2021-10-21 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 15:24 Jett Husher
2021-10-19 21:53 ` Bart Schaefer
2021-10-21 14:49 ` Daniel Shahaf [this message]
2021-10-22 4:43 ` Jett Husher
2021-10-25 19:36 ` Daniel Shahaf
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=20211021144926.GF16034@tarpaulin.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--cc=jetthusher@pm.me \
--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).