erc reconnects to channels on wrong servers (too)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
emacs22 (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
emacs23 (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
emacs24 (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
erc (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: erc
When ERC loses a connection and then regains it, if I have channels open on another server as well, it will reconnect to the other server's channels, too.
To reproduce (clumsily):
M-x erc-select <RET> server1 <RET> <RET> <RET>
M-x erc-select <RET> server2 <RET> <RET> <RET>
In the server1:ircd buffer:
/join #onetest <RET>
In the server2:ircd buffer:
/join #twotest <RET>
(This was slightly rearranged to cope with a related bug in new versions of Erc.)
Now jerk the connection to server2, or (as a rough approximation) kill the associated buffer server2:ircd
M-x kill-buffer <RET> server2:ircd <RET>
Then reconnect:
M-x erc-select <RET> server2 <RET>
Expected result:
ERC should rejoin #twotest on server2 but no other channels.
Actual result:
ERC joins back on #twotest but in addition joins #onetest on server2 (sic), resulting in a new buffer #onetest<2> (assuming you have the variable `uniquify-
Reproducible:
Always
I guess the list of active channels does not contain the information about which server a channel is on, or the information is simply not used when reconnecting to lost channels.
Changed in erc: | |
status: | New → Incomplete |
Changed in erc: | |
status: | New → Confirmed |
Changed in erc (Ubuntu): | |
status: | New → Confirmed |
Changed in emacs23 (Ubuntu): | |
status: | New → Confirmed |
Changed in emacs22 (Ubuntu): | |
status: | New → Confirmed |
Still happens on Feisty, for the record.