With the current git HEAD, for at least one of my jabber contacts, an unrequested group chat buffer will appear almost immediately after I open a regular buffer for that contact. if i close the groupchat buffer, it will not reappear as long as the regular buffer stays open. If I delete the regular buffer and open create it anew, the groupchat buffer reappears, too. The problem is reproducible for that contact. version 0.8.0 does not have it.
Sounds like an incoming message is incorrectly treated as a groupchat message. Could you set jabber-debug-log-xml to t and paste messages from that contact here?
I replaced the:
* name and host of that contact with HIS_NAME@HIS_HOST,
* my name and host with MY_NAME@MY_HOST, and
* my IP with MY_IP
* my password with PASSWORD
in the log. I also stripped all messages related to other contacts. The result is attached;
log
Right, I found the problem. In jabber-roster-ret-action-at-point, we try to DTRT, i.e. open a chat buffer if the roster item is a contact and a groupchat buffer if the roster item is a chatroom. Normally, jabber.el will refuse to open a groupchat buffer if the JID is not a chatroom (as determined by disco), but your contact's server returns a feature-not-implemented error in response to the disco info request. Since at least one MUC server actually does that (ejabberd's mod_irc), jabber.el will give it the benefit of the doubt and open a groupchat buffer anyway...
So... the right answer is probably to make RET in a roster buffer open a groupchat only if the JID actually says it's a groupchat, disabling the feature-not-implemented hack for this case, so you'd have to join non-compliant rooms with an explicit M-x jabber-muc-join.
Out of interest, could you check what server this is? I.e. M-x jabber-get-version or M-x jabber-get-disco-info on HIS_HOST.
version request log
they don't seem too eager to tell anyone anything.
there's a good chance they're running ejabberd, though.
(since i didn't get a mail that notified me of the attachment i just added, i'm making it explicit here)
Right, that's the behaviour you'd get from ejabberd with mod_disco disabled.
I just pushed a fix to git. Could you try it? It's a small change to jabber-roster.el.
That appears to fix it, thanks.
This change isn't in 0.8.91, right?
I'm affected as well by this annoyance, however I don't get where I can download the patch and how to apply it... tia and sorry for the silly question.
2 lufu: http://emacs-jabber.git.sourceforge.net/git/gitweb.cgi?p=emacs-jabber/emacs-jabber;a=patch;h=7c3e8e98ce458539efe2dd30b3051fbbed06cd01