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.

Sign up for GitHub

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

Jump to bottom

Apply incoming_me_translation to private messages, too #27

Closed
digitalcircuit opened this issue Apr 10, 2016 · 1 comment
Closed

Apply incoming_me_translation to private messages, too #27

digitalcircuit opened this issue Apr 10, 2016 · 1 comment
Labels
bug

Comments

@digitalcircuit
Copy link
Contributor

Right now, incoming_me_translation affects channel messages, but not private messages. As the /me command works in both situations in the official webclient, if possible, the Bitlbee Discord plugin should apply the translation to both situations.

It might simplify matters to move the code into a dedicated function for parsing incoming me strings.
@digitalcircuit digitalcircuit mentioned this issue Apr 10, 2016
Open
@sm00th sm00th added the bug label Apr 11, 2016
@sm00th
Copy link
Owner

sm00th commented Apr 11, 2016

Yup, you are right. Fixed in 0fc96b6.

@sm00th sm00th closed this as completed Apr 11, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sm00th @digitalcircuit