commit 7b9b1fc

Fix processing CHATHISTORY TAGMSG as standalone messages

Receiving a TAGMSG in chathistory causes the handler to return nil.

Previously this caused the handler to be called again without the
playblack flag, causing us to emit events out of their history context.

This meant we would show typing notifications for users from chathistory
batches.

Soju will soon be able to send TAGMSG messages in its chathistory, so
we're fixing that now.

 1@@ -655,8 +655,8 @@ func (s *Session) handleRegistered(msg Message) (Event, error) {
 2 					Target:   b.Target,
 3 					Messages: append(b.Messages, ev),
 4 				}
 5-				return nil, nil
 6 			}
 7+			return nil, nil
 8 		}
 9 	}
10 	return s.handleMessageRegistered(msg, false)