-
-
Notifications
You must be signed in to change notification settings - Fork 179
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
Invalid commands should not send as messages #390
Comments
A fix for this is in master, with the "Unknown command" message appearing in the console window. |
I use YouTrack at work and the jabber bot takes commands by prefixing the messages with a slash. This does not work as the slash isn't sent to the receiver. EDIT: EDIT2: |
Perhaps in the long run the command prefix character can be configured for profanity. For now I'll make it an option to disable/enable sending the I guess it would make sense to allow the user to escape the command prefix too, for example if your chat bot has a |
Yes I think that an escape character would be the best option because the commands could be the same both inside Profanity and for the receiver. In our case /help is a command for both. |
Now a double slash will escape the command and allow it to be sent e.g.:
Should send I went for Note that Please reopen the issue if you find any problems. |
Commands with leading slashes should not send to the recipient(s) in the current window, and should instead produce an error message, either on the current window or the status window.
The text was updated successfully, but these errors were encountered: