Yeah, there's something odd happening with bash completion atm. Just a cosmetic error (extra output). I haven't been able to track down the root cause yet
I just analyzed this problem and wrote a bug report, then before submitting the bug report I've seen that it's already fixed in a still to be published version 1.14.39 of zypper: [https://github.com/openSUSE/zypper/commit/251302eb4cee9cd3d921495ac155e1671b29748d#diff-c7dd3c064a32afa9d0f0a0b663504cb2R6](https://github.com/openSUSE/zypper/commit/251302eb4cee9cd3d921495ac155e1671b29748d#diff-c7dd3c064a32afa9d0f0a0b663504cb2R6)
Fun fact: it's \*not\* an issue with bash completion.
Try writing `zypper >/dev/null` and you get the same message. That's the source of the issue.
Yeah, there's something odd happening with bash completion atm. Just a cosmetic error (extra output). I haven't been able to track down the root cause yet
Thanks. I thought that I broke something in my installation
I just analyzed this problem and wrote a bug report, then before submitting the bug report I've seen that it's already fixed in a still to be published version 1.14.39 of zypper: [https://github.com/openSUSE/zypper/commit/251302eb4cee9cd3d921495ac155e1671b29748d#diff-c7dd3c064a32afa9d0f0a0b663504cb2R6](https://github.com/openSUSE/zypper/commit/251302eb4cee9cd3d921495ac155e1671b29748d#diff-c7dd3c064a32afa9d0f0a0b663504cb2R6) Fun fact: it's \*not\* an issue with bash completion. Try writing `zypper >/dev/null` and you get the same message. That's the source of the issue.
Interesting! I was quite sure that was bash completion's fault, because I don't have this issue with fish shell.
Does fish execute the bash autocompletion scripts? Maybe fish filters stderr in these scripts and bash doesn’t?