Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

Re: [BUG] process substitution breaks when nested or traverses a function



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@xxxxxxxxx> 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@xxxxxxxxx> 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@xxxxxxxxxxx> wrote:
>>> On Sun, 17 Jun 2018 00:14:10 -0300
>>> Francisco de Zuviría Allende <franciscodezuviria@xxxxxxxxx> 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
>>>
>>>



Messages sorted by: Reverse Date, Date, Thread, Author