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
Unable to join private group conversation #852
Comments
Which version/commit of wee-slack are you running? Try to enable debug mode and see if there are any messages in the core or debug buffer when you run the command. |
I'm using commit 64a4395 (master as of June 24). Here's an example of the debug messages I see when I try to join an existing group (don't know if all of these are related):
In contrast, when I try to join a group that never existed before, the |
So nothing is printed to the core buffer? Can you post the content that |
No, nothing shows up in the core buffer. (I do actually see an error message Here's an example of the response when the
If the response is different when it's successful, I don't know an easy way to find that out, because it's only successful the first time (and the URL is the same each time.) |
Following kludge seems to allow joining conversations with
I'm sure there is a better way to do this. Of course this still doesn't create the buffer automatically, you need to manually invoke |
This should be fixed now. Both that the buffer is not shown when you start WeeChat, and that Please comment or open a new issue if you still experience issues. |
I received an email saying that I was mentioned in a private group conversation ("mpdm-alice--bmoody--bob-1", I guess, is the internal identifier.)
When I open weechat, there is no buffer for this conversation. (I guess that this is due to issues #551 and/or 780).
However, when I type
/slack talk alice,bob
, nothing happens. No buffer is created and there is no error message.It appears that I can create new conversations with different sets of people, but for some reason I cannot join a conversation that already exists.
The text was updated successfully, but these errors were encountered: