-
Notifications
You must be signed in to change notification settings - Fork 87
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
BUG: Issue with command parsing #79
Comments
seems silly to have a chat interface with potential to execute a command by accident without some kind of prefix like a slash for commands and say ! for bot stuff. |
That too.
|
The prefix was removed so that the chat has a more command-line-y feel (there's been two: |
should be consistent. |
(I agree too, but I wanted to see how other people felt about it, and which commands are named the worst) |
Running a command like
ls anything_here
will throw an error like
ls: anything_here Permission denied
but still run the base command afterwards.
The text was updated successfully, but these errors were encountered: