search

sshirokov / ZNC.el

Make ERC and ZNC get along more goodest.
MIT License
56 stars 20 forks source link

Connecting to multiple networks causes erratic behavior #13

Open rschuetzler opened 9 years ago

rschuetzler commented 9 years ago

I have a ZNC bouncer set up with one account connecting to multiple networks. Using znc-erc to connect to a single network works great, but upon connecting to the second network, either with znc-erc, or immediately with znc-all, everything goes crazy. Every IRC buffer with changed content gets automatically pulled up in the right-side frame. I can kill the frame, but it comes back at some point no matter what I do. I also cannot figure out a way to see my channels on the second network.

Also, once I connect to the second network, all of my messages begin showing up duplicated and all spaced out.

jeroentbt commented 9 years ago

That does not happen here.

strugee commented 9 years ago

That does not happen here.

You're probably running an older version of ZNC.

@rschuetzler this seems like a dupe of #9?

jeroentbt commented 9 years ago

@strugee I am running a bit behind indeed (ZNC 1.4)

strugee commented 9 years ago

@jeroentbt I'm running 1.4, too. That's not sufficiently far behind to not trigger this bug... weird that you're not seeing it. Do you have multiple networks in one user?

jeroentbt commented 9 years ago

@strugee yes, two (debian and freenode)

I have this set up in my config:

(setq znc-servers (quote (("my.znc.host" 16667 t (
    (freenode "jeroen/freenode" "hunter2")
    (debian "jeroen/debian" "hunter2"))))))
strugee commented 9 years ago

@jeroentbt Well, that's why you're not seeing it. You're duplicating the network in the username. The point of #14 is tor ZNC.el to use the network slug, and have the username be the same. E.g.:

(setq znc-servers
      '(("znc.example.org" 1337 t
     ((freenode "alex" "hunter2")
      (moznet "alex" "hunter2")
      (oftc "alex" "hunter2")
      (gimpnet "alex" "hunter2")))))
jeroentbt commented 9 years ago

I used to have it like that but then I got two network buffers, both connecting to OFTC (referenced as debian in my config).

Furthermore, in those network buffer I get:

09:41:28 -*status- You have several networks configured, but no network was specified for the
                   connection.
09:41:28 -*status- Selecting network [debian]. To see list of all configured networks, use /znc
                   ListNetworks
09:41:28 -*status- If you want to choose another network, use /znc JumpNetwork <network>,
                   or connect to ZNC with username jeroen/<network> (instead of just jeroen)

Hence the user/network

strugee commented 9 years ago

I used to have it like that but then I got two network buffers, both connecting to OFTC (referenced as debian in my config).

Yes. That's exactly what this bug is describing.

rschuetzler commented 8 years ago

Put the network slug in the username. So rather than:

 (moznet "alex" "hunter2")

you need to include the slug in the username like so:

(moznet "alex/moznet" "hunter2")

This is one of ZNC's built-in methods for dealing with multiple networks for the same user.

strugee commented 8 years ago

@hammerheadlemon you could also do what I do and patch ZNC.el with #14.