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

Begin to add categories #902

Closed
wants to merge 9 commits into from
Closed

Begin to add categories #902

wants to merge 9 commits into from

Conversation

xPMo
Copy link
Contributor

@xPMo xPMo commented Feb 28, 2020

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:

  1. 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.

  2. After this division, a further division into subcategories can be done. Probably something like:

  • OS: filesystem, system packages, LAN/WAN, $TERM
  • lang-agnostic dev/services: VCS, docker, aws,
  • lang-specific: nvm, pyenv, jquery
  1. I certainly don't want to examine every plugin. I encourage anyone looking at this to grab a handful of uncategorized plugins and decide where they should go, make a PR to the category branch.

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

  • This document is covered by the BSD License, and I agree to contribute this PR under the terms of the license.

The primary purpose of these plugins is
to provide new functions or aliases.

<!-- TODO -->
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TODO found

Copy link
Contributor Author

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 -->
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TODO found

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know.

@codeclimate
Copy link

codeclimate bot commented Feb 28, 2020

Code Climate has analyzed commit c9e19b6 and detected 2 issues on this pull request.

Here's the issue category breakdown:

Category Count
Bug Risk 2

View more on Code Climate.

@xPMo xPMo changed the title Begin to add categories (#89) Begin to add categories Feb 28, 2020
@unixorn
Copy link
Owner

unixorn commented May 2, 2021

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 git, ruby and python status decorations"

@unixorn unixorn closed this May 2, 2021
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

Successfully merging this pull request may close these issues.

2 participants