-
-
Notifications
You must be signed in to change notification settings - Fork 550
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
Begin to add categories #902
Conversation
The primary purpose of these plugins is | ||
to provide new functions or aliases. | ||
|
||
<!-- TODO --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO found
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know.
and/or hook into other actions taken by the shell | ||
(such as changing directory or executing a command). | ||
|
||
<!-- TODO --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO found
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know.
Code Climate has analyzed commit c9e19b6 and detected 2 issues on this pull request. Here's the issue category breakdown:
View more on Code Climate. |
Closing. Sorting into sub-categories is too much maintenance. That said, I'm not opposed to adding tags inline in entries, like the current "includes |
This is a quick and dirty start of separating plugins into categories (ref: #89 ). Completions have already been done, but I moved more into that category. I added a category for ZLE plugins (bindings and syntax highlighting) and moved all I could find there.
A few things:
Before I or others move too much around, I would like a discussion on how best to split the remaining plugins. My current proposal is into "command" plugins (directly adds user-facing functions/aliases) and "environment" plugins (adds hooks, sets environment variables, etc.). I made sure to add the language "This plugin primarily..." underneath each heading, since many plugins do both.
After this division, a further division into subcategories can be done. Probably something like:
Again, discussion is encouraged. @unixorn, would you rather me accept category-related PRs into xPMo/awesome-zsh-plugins:categories, or would you prefer to own the branch?
Copyright Assignment