From: Peter Stephenson <p.stephenson@samsung.com>
To: <zsh-workers@zsh.org>
Subject: Re: <(...), >(...) and fds above 9
Date: Tue, 2 Jul 2019 16:21:27 +0100 [thread overview]
Message-ID: <1562080887.5684.26.camel@samsung.com> (raw)
In-Reply-To: <20190702151918.iysfgd4tpb37ladw@chaz.gmail.com>
On Tue, 2019-07-02 at 16:19 +0100, Stephane Chazelas wrote:
> 2019-07-02 13:12:35 +0000, Peter Stephenson:
> >
> > On Tue, 2019-07-02 at 13:20 +0100, Stephane Chazelas wrote:
> > >
> > > 2019-07-02 09:59:36 +0100, Peter Stephenson:
> > > Note that ksh93 marks the fds above 2 that are open with
> > > exec (exec 7< file or exec {fd}< file) with close-on-exec
> > > (independently of whether the exec is done in background or
> > > not)
> > This will do that for file descriptors managed with varid or builtins from
> > modules, though it doesn't change the behaviour for file descriptors
> > managed directly by number. I'm wondering if that's too traditional to
> > be worth any pain of changing --- {fd} is a much more manageable
> > interface.
> [...]
>
> Note that I was not suggesting that zsh should do the same. That
> close-on-exec on ksh93 adds more confusion than it helps. No
> other shell does it AFAIK. That means that you need to work
> around it like:
That's fine, no need to commit it.
pws
next prev parent reply other threads:[~2019-07-02 15:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190701100058epcas2p25e5f8dbd14d048fe2be1d831f3cf60ab@epcas2p2.samsung.com>
2019-07-01 10:00 ` Stephane Chazelas
2019-07-01 10:08 ` Peter Stephenson
2019-07-01 14:39 ` Bart Schaefer
2019-07-01 15:28 ` Peter Stephenson
2019-07-01 16:22 ` Stephane Chazelas
2019-07-01 16:52 ` Peter Stephenson
2019-07-01 17:00 ` Peter Stephenson
2019-07-01 20:00 ` Stephane Chazelas
2019-07-01 20:06 ` Bart Schaefer
2019-07-02 8:59 ` Peter Stephenson
2019-07-02 12:20 ` Stephane Chazelas
2019-07-02 13:12 ` Peter Stephenson
2019-07-02 15:19 ` Stephane Chazelas
2019-07-02 15:21 ` Peter Stephenson [this message]
2019-07-02 16:43 ` Sebastian Gniazdowski
2019-07-02 18:08 ` 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=1562080887.5684.26.camel@samsung.com \
--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).