Bug #1305
When connected to irssiproxy, quassel reports messages sent from irssi in the wrong buffer/window/
0%
Description
I have set up irssi to listen as proxy.
In that mode, it acts a bit like a bouncer.
I connected quasselcore to that.
(I know, that is a bit strange, but whatever.)
When I send a message from irssi to user test, in a query, the following message is forwarded to quassel:
:JCaesar!julius@proxy PRIVMSG test :testmsg
Quassel interprets that as message from someone with my own nick and opens a new query window with my nick on it instead of putting it into the query for "test".
I have patched my quassel to stop doing that, so I don't care whether it is fixed. I just wanted to report it and drop the diff:
diff --git a/src/core/ircparser.cpp b/src/core/ircparser.cpp
index acc765a..5cf0c26 100644
--- a/src/core/ircparser.cpp
+++ b/src/core/ircparser.cpp@ -189,6 +189,12
@ void IrcParser::processNetworkIncoming(NetworkDataEvent *e)
msg = decrypt(net, target, msg);
+ // When quassel is behind a proxy, a message may appear with our nick as sender.
+ // Work that around
+ if (net->myNick() == senderNick) {
+ target = params0;
+ }
+
events << new IrcEventRawMessage(EventManager::IrcEventRawPrivmsg, net, msg, prefix, target, e->timestamp());
}
}