unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Barry Warsaw <barry@python.org>
To: emacs-devel@gnu.org
Subject: ERC problem with duplicate channel names on different servers?
Date: Tue, 9 Dec 2014 11:15:38 -0500	[thread overview]
Message-ID: <20141209111538.71a314ff@anarchist.wooz.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1667 bytes --]

Hello emacsers,

I think I am seeing a bug in erc, but before I submit a bug report, I wanted
to see if this problem is already known (I searched the emacs-bug Gmane
newsgroup to no avail) or if anybody already has a workaround.

FTR: emacs 24.4.1, Ubuntu 15.04, bip 0.8.9

So I use bip as my IRC proxy, connecting to multiple networks, including
freenode, OFTC, and an internal corporate server.  This arrangement has been
working great for years.

Today I just configured bip to join two channels which have the same name on
freenode and the internal server, and erc started acting funny.  The problem
could of course be bip, and I will work on eliminating that possibility, but
this *feels* like an erc problem.

Strange thing 1: no erc buffer comes up with the channel name on freenode.
This channel is rather light traffic, but the only buffer with the shared
channel name that exists is the #channel@internal buffer.  I can join
#channel@freenode in xchat just fine.

Strange thing 2: In the #channel@freenode buffer, suddenly all nick completion
(TAB) is broken.  Nick completion in all other channel buffers continues to
work as expected.

Strange thing 3: When #channel@internal is visible in one emacs window, but I
am editing a file in another window and someone pings my nick in the internal
channel, erc will pop up the channel buffer.  Usually this only happens if the
ping happens in a non-visible buffer.  It's as if erc is seeing the nick ping
in the visible buffer (#channel@internal) but thinks its happening in the
hidden buffer (#channel@freenode - which doesn't exist afaict).

Any thoughts?

Cheers,
-Barry

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

                 reply	other threads:[~2014-12-09 16:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141209111538.71a314ff@anarchist.wooz.org \
    --to=barry@python.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).