Jeff Widman

@belak Is this still relevant given that #1810 appears to fix the root issue? Or were there other problems with `zsh-async` such that you want to continue pursuing this?

Gotcha... yeah, Idk either... Microsoft/windows has been changing a lot to be more linux-friendly, I would probably vote to let this sit a bit and see if they provide easier...

It's this line: https://github.com/sorin-ionescu/prezto/commit/d686da3c039a1ed0ae271860d271ec966f59c16a#diff-414db2cc4cb0c69d0fea2d6304ceb9921bf9d0d96f8d47f545e19bfa217dc39dR37 Specifically, the chang from `$+commands[python]` to `$#commands[(i)python[23]#]` that causes the problem. Adding basic `echo` statements and the new version doesn't catch python so it returns early....

> Are you seeing the same problem as in #1416, or is it a separate issue? > If it is that issue, this patch, should re-add that hack... I suspected...

Non-working: * `$#commands[(i)python[23]#]` * `$commands[(i)python[23]]` Working: * `$+commands[(i)python[23]#]` * `$#commands[(i)python[23]]` * `$+commands[(i)python[23]]` So it's related to the `#`. I'm not sure what they do though... checking the docs, but if...

I did some reading, and still not totally clear, but that may be because it's an hour past normal bed time. I'll re-read in the morning. @indrajitr if you happy...

Sorry for the delay here, been on vacation in the mountains. @indrajitr thanks for the detailed explanation! Here's the output as requested: ``` ~ ❯❯❯ echo $commands[(I)python[23]#] python3 python ~...

Yes, that's correct: ``` ~ ❯❯❯ echo $commands[(i)python[23]] python3 ~ ❯❯❯ echo $commands[(i)python[23]#] python3 ~ ❯❯❯ echo $#commands[(i)python[23]#] 1 ```

Yep, both find a python as expected: ``` ~ ❯❯❯ if (( ! $#commands[(i)python[23]#] && ! $+functions[pyenv] )); then echo "Python not there"; fi ~ ❯❯❯ if (( ! $+commands[(i)python[23]#]...

Also, @indrajitr if it'd be faster, happy to do a quick call sometime when our timezones overlap and do a video call and try to work through this together. I...