| 2007-11-05 07:46:49 |
era |
bug |
|
|
added bug |
| 2008-01-11 08:31:36 |
Michael Olson |
bug |
|
|
added attachment 'erc_5.2.git.20080111-0ubuntu1_all.deb' (erc_5.2.git.20080111-0ubuntu1_all.deb) |
| 2008-01-11 08:38:57 |
Michael Olson |
bug |
|
|
added attachment 'erc_5.2.git.20080111-0ubuntu1_all.deb' (erc_5.2.git.20080111-0ubuntu1_all.deb) |
| 2008-01-30 01:52:06 |
Michael Olson |
erc: status |
New |
Incomplete |
|
| 2008-06-02 06:00:23 |
era |
erc: status |
Incomplete |
New |
|
| 2008-11-12 04:32:39 |
Daniel T Chen |
erc: status |
New |
Confirmed |
|
| 2008-11-12 04:32:39 |
Daniel T Chen |
erc: statusexplanation |
Yes, I still get this with the standalone erc 5.3-1ubuntu1 on emacs22 on Hardy amd64.
To make the repro steps more effective, one could create an SSH tunnel from localhost 6666 to some remote IRC server -- the SSH crypto is irrelevant here, the point is just to give you an easy way to establish a second server, and disconnect and reconnect it at will. |
|
|
| 2008-12-09 18:53:04 |
era |
bug |
|
|
assigned to emacs22 (Ubuntu) |
| 2009-02-21 15:08:20 |
Anselm Helbig |
erc: status |
Confirmed |
Incomplete |
|
| 2009-02-21 15:08:20 |
Anselm Helbig |
erc: statusexplanation |
|
I could not reproduce this behavior on intrepid/i686 with emacs22-gtk-22.2-0ubuntu2 and erc-5.3-1ubuntu1. |
|
| 2009-02-21 15:11:46 |
Anselm Helbig |
emacs22: status |
New |
Incomplete |
|
| 2009-02-21 15:11:46 |
Anselm Helbig |
emacs22: statusexplanation |
|
I can not reproduce this issue on intrepid/i686 with the builtin erc of emacs22-gtk-22.2-0ubuntu2.
@era: are you absolutely sure that you're not accidentally using an older version that you installed locally? What does M-x locate-library <RET> erc <RET> print out? |
|
| 2009-02-23 09:17:39 |
era |
emacs22: status |
Incomplete |
New |
|
| 2009-02-23 09:17:39 |
era |
emacs22: statusexplanation |
I can not reproduce this issue on intrepid/i686 with the builtin erc of emacs22-gtk-22.2-0ubuntu2.
@era: are you absolutely sure that you're not accidentally using an older version that you installed locally? What does M-x locate-library <RET> erc <RET> print out? |
Library is file /usr/share/emacs/22.2/lisp/erc/erc.elc
erc-version-string is a variable defined in `erc.el'.
Its value is "Version 5.2"
I can still trivially reproduce with the kill-buffer maneuvre. The obvious indication is that there is now a second buffer #onetest<2> where erc has joined #onetest on server2 |
|
| 2009-02-23 15:04:43 |
era |
erc: status |
Incomplete |
New |
|
| 2009-02-23 15:04:43 |
era |
erc: statusexplanation |
I could not reproduce this behavior on intrepid/i686 with emacs22-gtk-22.2-0ubuntu2 and erc-5.3-1ubuntu1. |
|
|
| 2009-02-23 15:08:24 |
era |
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>
/join #onetest <RET>
M-x erc-select <RET> server2 <RET> <RET> <RET>
/join #twotest <RET>
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).
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. |
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-buffer-name-style' set to its default value).
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. |
|
| 2010-09-17 16:35:23 |
rusivi2 |
erc (Ubuntu): status |
New |
Incomplete |
|
| 2010-09-17 16:35:38 |
rusivi2 |
emacs22 (Ubuntu): status |
New |
Incomplete |
|
| 2010-10-06 07:21:38 |
era |
bug task added |
|
emacs23 (Ubuntu) |
|
| 2010-10-06 07:25:39 |
era |
emacs22 (Ubuntu): status |
Incomplete |
New |
|
| 2010-10-06 07:27:23 |
era |
erc (Ubuntu): status |
Incomplete |
New |
|
| 2012-11-13 15:58:19 |
Thomas Hotz |
erc (Ubuntu): status |
New |
Confirmed |
|
| 2012-11-13 15:58:22 |
Thomas Hotz |
emacs23 (Ubuntu): status |
New |
Confirmed |
|
| 2012-11-13 15:58:28 |
Thomas Hotz |
emacs22 (Ubuntu): status |
New |
Confirmed |
|
| 2012-11-13 15:58:30 |
Thomas Hotz |
bug |
|
|
added subscriber Thomas Hotz |
| 2014-09-11 08:56:57 |
era |
bug task added |
|
emacs24 (Ubuntu) |
|
