From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Zach Riggle <zachriggle@gmail.com>,
Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Where is this =(:) construct documented?
Date: Fri, 11 Jun 2021 21:58:38 +0200 [thread overview]
Message-ID: <CAN=4vMp1EUqUzATk5EVPWWYv3aO+8E94_MRQjeBywZ=_KgczfA@mail.gmail.com> (raw)
In-Reply-To: <20210611195322.4tnhhppbjpddi2tv@chazelas.org>
On Fri, Jun 11, 2021 at 9:53 PM Stephane Chazelas <stephane@chazelas.org> wrote:
>
> That's the third form of process substitution.
And the colon in =(:) is a builtin that does nothing (the same as
true). It's mandated by POSIX.
Roman.
next prev parent reply other threads:[~2021-06-11 19:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 19:17 Zach Riggle
2021-06-11 19:18 ` Zach Riggle
2021-06-11 19:53 ` Stephane Chazelas
2021-06-11 19:58 ` Roman Perepelitsa [this message]
2021-06-11 20:04 ` Stephane Chazelas
2021-06-11 20:39 ` Zach Riggle
2021-06-14 12:44 ` Vincent Lefevre
2021-06-14 14:32 ` Stephane Chazelas
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='CAN=4vMp1EUqUzATk5EVPWWYv3aO+8E94_MRQjeBywZ=_KgczfA@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=zachriggle@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).