You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 21, 2022. It is now read-only.
When I try to connect to other instance of weechat, I'm asked whether the other connection should be replaced. If I refuse, no connection is made, if I agree, former connection is closed.
There should be no reason for this limitation.
The text was updated successfully, but these errors were encountered:
When I try to connect to other instance of weechat, I'm asked whether
the other connection should be replaced. If I refuse, no connection is
made, if I agree, former connection is closed.
Unfortunately I didn't think of multiple connections when writing
weechat.el. This results in a fairly big "singleton" that holds the data
of available channels, connection information, relevant buffers, etc.
Changing this would be quite a refactoring and I don't have plans to add
this in the foreseeable future.
I'm happy to review any Pull Requests working in this direction.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When I try to connect to other instance of weechat, I'm asked whether the other connection should be replaced. If I refuse, no connection is made, if I agree, former connection is closed.
There should be no reason for this limitation.
The text was updated successfully, but these errors were encountered: