WIP: Fix unexpected responses from the server

[laughedelic]

Addresses #4091.

85ab082 should fix the first problem.

And I think the second one sits here:

sbt/main/src/main/scala/sbt/internal/CommandExchange.scala

Lines 250 to 256 in 7ae83cc

	case _ =>
	channels collect {
	case c: ConsoleChannel =>
	c.publishEvent(event)
	case c: NetworkChannel =>
	try {
	c.publishEvent(event)

But I'm not sure how to fix it. In this case it matches any events (so we cannot check channel name here) and redirects them to the NetworkChannel.publishEvent which already doesn't check if the channel name matches.

On the other hand there is also publishEventMessage method which handles ExecStatusEvent and checks channel name. So probably we could reuse it here.

I'm not sure what is the general intent of this piece of code quoted above: if it's not a StringMessage, just broadcast is on all channels? Even if we want to do that, publishEvent is not a good choice, probably using langNotify or something similar would be better.

[dwijnand]

sadly I can't help much with the other part, because the general intent is not clear to me either.