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

BUG: Issue with command parsing #79

Closed
emma-miler opened this issue Mar 16, 2022 · 5 comments
Closed

BUG: Issue with command parsing #79

emma-miler opened this issue Mar 16, 2022 · 5 comments

Comments

@emma-miler
Copy link

Running a command like
ls anything_here
will throw an error like
ls: anything_here Permission denied
but still run the base command afterwards.

@ghost
Copy link

ghost commented Mar 16, 2022

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.

@emma-miler
Copy link
Author

emma-miler commented Mar 16, 2022

That too.
In my humble opinion commands should

  1. be filtered from chat, and
  2. have a prefix

@quackduck
Copy link
Owner

The prefix was removed so that the chat has a more command-line-y feel (there's been two: /, ./). I can add prefixes to some of the commands; which do you think are the most problematic?

@ghost
Copy link

ghost commented Mar 16, 2022

should be consistent.

@quackduck
Copy link
Owner

(I agree too, but I wanted to see how other people felt about it, and which commands are named the worst)

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

No branches or pull requests

2 participants