Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connecting to multiple networks causes erratic behavior #13

Open
rschuetzler opened this issue Nov 1, 2014 · 10 comments
Open

Connecting to multiple networks causes erratic behavior #13

rschuetzler opened this issue Nov 1, 2014 · 10 comments

Comments

@rschuetzler
Copy link

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
Copy link

That does not happen here.

@strugee
Copy link

strugee commented Aug 5, 2015

That does not happen here.

You're probably running an older version of ZNC.

@rschuetzler this seems like a dupe of #9?

@jeroentbt
Copy link

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

@strugee
Copy link

strugee commented Aug 6, 2015

@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
Copy link

@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
Copy link

strugee commented Aug 6, 2015

@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
Copy link

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
Copy link

strugee commented Aug 7, 2015

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
Copy link
Author

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
Copy link

strugee commented Nov 14, 2015

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants