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

Direct message not opening when receiving first message #551

Closed
lzmartinico opened this issue Apr 9, 2018 · 8 comments · Fixed by #859
Closed

Direct message not opening when receiving first message #551

lzmartinico opened this issue Apr 9, 2018 · 8 comments · Fixed by #859
Labels

Comments

@lzmartinico
Copy link

When I receive a new message from a team member I have never talked to, the direct message channel isn't automatically opened

@trygveaa
Copy link
Member

By "not automatically opened", do you mean that the buffer isn't created, or that weechat doesn't switch to the buffer?

What should happen is that a buffer is created in the background, and the number that buffer gets is shown in the hotlist.

@lzmartinico
Copy link
Author

Sorry, I meant no buffer got created, or at least no number appeared in the hotlist

@tardypad
Copy link

I just noticed the same issue myself.
I have a couple of new people that sent me direct messages but no buffer has been created.
I just found it out while opening slack in the browser. It made it look like I ignored those people I guess :/

IIRC the following works: if my weechat is open and a new person talks to me, then the buffer is created.
I believe that maybe what doesn't work then is to have the new buffers created after starting weechat itself.

@antoyo
Copy link

antoyo commented Jun 13, 2019

Same issue here.
Could you please fix this issue?

@trygveaa
Copy link
Member

trygveaa commented Jun 13, 2019

I'm not able to reproduce the issue. Can you give me some more details? Like does it happen for messages from all users or only some? If only some, is there any commonalities between those? Have you talked to these people previously? Do the buffers appear after you reload the script, or are they still missing?

Also, try to enable debug mode and see if any errors are printed in the core or debug buffers when the problem occurs.

@antoyo
Copy link

antoyo commented Jun 13, 2019

I can reproduce as such:

/join Slackbot
/slack slash /remind in 1 minute Test
/close
/quit

Start weechat after a couple of minutes and the buffer Slackbot won't be opened (if you see the Slackbot buffer, please repeat the above steps, it does not happen everytime).
I will edit this messages to post the other messages you mentionned.

I'd say it happens for most users, even groups (buffer with multiple people direct messaging).
I have talked to some of these people before, but it happens even with people that I never talked to before.

In debug mode, there's nothing interesting:
It says it connected to Slack in the first buffer and the debug buffer says:

DEBUG: Couldn't load emoji list: IOError: [Errno 2] No such file or directory: u'~/.weechat/weemoji.json'

@antoyo
Copy link

antoyo commented Jun 18, 2019

Are you able to reproduce with the above steps?

@trygveaa
Copy link
Member

Yeah, thanks, I can reproduce it with that. But I don't have time to look into it right now.

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

Successfully merging a pull request may close this issue.

4 participants