Closed hexium310 closed 2 weeks ago
Thanks for testing it before the release. I had interactive_comments
enabled, which prevented the error from occurring when I tested it.
Comments within a command substitution inside a function are not automatically removed when parsed, unlike other comments in a function. Therefore, moving the comment outside of the substitution should not trigger any error.
Options:
setopt localoptions interactive_comments
Option 1 seems safe, and one can use git blame
to check why the line was written that way.
Option 2 should work, but who knows what kind of pitfalls this might unleash.
Option 3 makes the comment one line separated from the actual affected code line, which looks odd.
EDIT1
Related thread on the Zsh Mailing List Archive:
Thanks!
After 22adb6494f4957d0bcc29a821b738b4e5d5796a5, the Zsh completion using
**
fails.The cause of this bug is that a comment is in the command substitution.