pkgx stderr output interfering with neovim plugins

[fredrikaverpil]

I just got hit by an issue seemingly stemming from that Go is compiled in a way so that it causes printouts of compiler warnings.

This is not how Go provided by Homebrew behaves. Would it make sense to try and sync the way you build Go to the way Homebrew builds Go?

EDIT: I was mistaken, title updated to better match actual problem.

[michaelessiet]

@jhheider what are your thoughts on this. Is this something that we can fix or is it out of our control?

[jhheider]

The resolving output of pkgx was messing up the neovim plugin. Silencing the shim lets it behave like "normal" go. Was wondering if you think silencing shims in general might be wise. Or lowering their verbosity.

[IpongJkBase]

Yess

[Lazycryp]

that's it.....

[mxcl]

K I replied in that ticket to get more info. As said we already take two precautions to not output unless the recipient really wants it. This is the first time we have found a project where that is not enough.

I don't want to silence all output for shims. That would mean that a completely undefined amount of time may elapse with no information to the user at all about what is happening if projects need to be cached.

So lets see what this project says. I would be interested to understand why they are reading stderr and why they are presenting themselves to us as a terminal.

[mxcl]

In the meantime, edit the go shim and add --silent after pkgx. Once we understand what's going on here we'll try to do what is best for everyone.

[sambojix]

I think this is a natural thing, because this can be an input for tea developers to look for mistakes to build a more advanced ecosystem in the future....This can be an input....and it is natural because this is just the beginning🙏🙏

[HubbusBubbus]

It's fine