zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Cc: tvboyd23@gmail.com
Subject: Re: Documentation about Multios is misleading, and perhaps untrue
Date: Thu, 11 Oct 2018 12:12:40 -0700	[thread overview]
Message-ID: <CAH+w=7ZMCr9qDUM9MBXKf4C8nu=HV4TTVOQdsB-gb=oJGDVB4g@mail.gmail.com> (raw)
In-Reply-To: <8B27B616-9DDE-4A04-AA05-2EA7234051A0@dana.is>

On Wed, Oct 10, 2018 at 9:05 PM dana <dana@dana.is> wrote:
>
> On 10 Oct 2018, at 21:33, Tom Boyd <tvboyd23@gmail.com> wrote:
> >What should be done about this ?
>
> Not sure if there's really an issue with the rest

A bit of common sense has to be applied here.  These are redirection
operators and are going to behave first like redirection operators,
which means that the shell is going to open the file descriptors
before executing any of the commands, and then pass those descriptors
around.  The semantics of redirections demands this.  An external
command like "cat" receives a list of names in its argument list and
processes the names one by one, so it can completely open and close
the file with each name before moving on to the next one, but the
shell can't do that and would be broken in other cases if it tried.

It's pointless to try to call call out every possible instance where
the fundamental semantics of shell operations affect a particular use
of the syntax.

  reply	other threads:[~2018-10-11 19:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11  2:33 Tom Boyd
2018-10-11  4:05 ` dana
2018-10-11 19:12   ` Bart Schaefer [this message]
2018-10-11 20:35     ` Daniel Shahaf
2018-10-11 20:59       ` Bart Schaefer
2018-10-12  8:30         ` Peter Stephenson
2018-10-16  0:45           ` Tom Boyd
2018-10-16  2:07             ` Daniel Shahaf
2018-10-16  9:33               ` Peter Stephenson

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='CAH+w=7ZMCr9qDUM9MBXKf4C8nu=HV4TTVOQdsB-gb=oJGDVB4g@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=tvboyd23@gmail.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).