Run go tools cover

[eaburns]

Make sure that we didn't miss anything obvious.

[chrissexton]

Missing coverage:

• Command.String
• Message.String
• Read
• read:
  • stripping the '\n' character (do we even want this?)
  • EOF after a '\r'
• junk:
  • last return statement
  • break statement

[mccoyst]

Regarding the '\n' thing, here's where that happened: https://code.google.com/p/velour/issues/detail?id=30

Looking at the code, it's not obvious to me how the extra '\n' got in there.

[chrissexton]

Perhaps if it is a velour specific issue, putting any '\n' characters into your messages should be an error and the responsibility of stripping them is the client's problem.

[mccoyst]

I think it'd be nice of velour to split messages on '\n' — we already have the functionality for long messages.

This specific extra '\n' was being added after the "\r\n" that terminates the IRC message; not the PRIVMSG content that the user entered.