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

should there be a distinction between built-in commands/custom commands #49

Closed
Luis-Henriquez-Perez opened this issue Mar 31, 2021 · 1 comment
Closed

should there be a distinction between built-in commands/custom commands #49

Luis-Henriquez-Perez opened this issue Mar 31, 2021 · 1 comment
Labels
simplification Making things simpler

Comments

@Luis-Henriquez-Perez
Copy link
Contributor

I am not sure if it is worth having a distinction between built-in commands and custom commands. Main benefit I see of it is the user won't accidentally get rid of built-in commands.
@okamsn okamsn added the simplification Making things simpler label May 8, 2021
@okamsn
Copy link
Owner

okamsn commented Jun 27, 2021

I've removed the distinction.

  • loopy-custom-command-aliases is now an alias of loopy-command-aliases.
  • loopy-custom-command-parsers is now an alias of loopy-command-parsers.

@okamsn okamsn closed this as completed Jun 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
simplification Making things simpler
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@okamsn @Luis-Henriquez-Perez