From: "Francisco de Zuviría Allende" <franciscodezuviria@gmail.com>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: zsh-workers@zsh.org
Subject: Re: [BUG] process substitution breaks when nested or traverses a function
Date: Wed, 27 Jun 2018 06:18:20 -0300 [thread overview]
Message-ID: <CA++-COwW3yuTuX3LbAu1oVuyWedbZrFWkqPR6WfVr0XX7AOsYA@mail.gmail.com> (raw)
In-Reply-To: <CA++-COx730-knwwYjR3y4jELnZvmC1ogPnwCGta24QmHw=Nncg@mail.gmail.com>
silly me, I forgot to fire up zsh while logged as root.
The problem persists :(
Maybe a regression from 5.5.1 ?
On Wed, Jun 27, 2018 at 6:14 AM, Francisco de Zuviría Allende
<franciscodezuviria@gmail.com> wrote:
> I created https://github.com/robbyrussell/oh-my-zsh/issues/6951
> Hopefully some can narrow down the problem
>
> On Wed, Jun 27, 2018 at 6:04 AM, Francisco de Zuviría Allende
> <franciscodezuviria@gmail.com> wrote:
>> I have zsh 5.5.1 in Debian Testing.
>>
>> I can confirm it is fixed. HOWEVER, in a shell that uses the oh my zsh
>> framework, the bug persists! (even if I disable all plugins)
>>
>> I had to login as root (which has no .zshrc) to make foo() { cat <(cat
>> "$@"); }; foo <(echo bar); work
>>
>> I will report in oh my zsh as well, but I don't think it's their
>> fault, and I don't think they'll be able to do anything about it.
>> declaring a foo and using cat should work, regardless of how many
>> functions have been loaded previously. There's something messing
>> zsh...
>>
>>
>> On Mon, Jun 18, 2018 at 6:28 AM, Peter Stephenson
>> <p.stephenson@samsung.com> wrote:
>>> On Sun, 17 Jun 2018 00:14:10 -0300
>>> Francisco de Zuviría Allende <franciscodezuviria@gmail.com> wrote:
>>>> This problem still happens.
>>>> > #!/bin/zsh
>>>> > foo() { cat <(cat "$@"); }; foo <(echo bar);
>>>> > cat: /proc/self/fd/11: No such file or directory
>>>
>>> This was fixed in 5.5. There's now a test for it at the end of
>>> D03procsubst.ztst, so failures will get picked up.
>>>
>>>> There is still no bug tracking system for zsh, right?
>>>
>>> No, we've never had a volunteer to look after one. The list is the
>>> right place to report bugs.
>>>
>>> pws
>>>
>>>
next prev parent reply other threads:[~2018-06-27 9:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180421093602epcas1p4c7f4182661b42fa2e477f8fe61a3e132@epcas1p4.samsung.com>
2018-04-21 9:35 ` Francisco de Zuviría Allende
2018-04-24 9:43 ` Peter Stephenson
2018-04-24 10:30 ` Daniel Shahaf
2018-04-24 10:47 ` Peter Stephenson
2018-04-24 11:09 ` Martijn Dekker
2018-04-24 12:29 ` Peter Stephenson
2018-06-17 3:14 ` Francisco de Zuviría Allende
2018-06-18 9:28 ` Peter Stephenson
2018-06-27 9:04 ` Francisco de Zuviría Allende
2018-06-27 9:14 ` Francisco de Zuviría Allende
2018-06-27 9:18 ` Francisco de Zuviría Allende [this message]
2018-06-28 18:37 ` Daniel Tameling
2018-06-29 8:37 ` 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=CA++-COwW3yuTuX3LbAu1oVuyWedbZrFWkqPR6WfVr0XX7AOsYA@mail.gmail.com \
--to=franciscodezuviria@gmail.com \
--cc=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).