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

commands for managing plugins #663

Closed
banister opened this issue Jul 23, 2012 · 4 comments
Closed

commands for managing plugins #663

banister opened this issue Jul 23, 2012 · 4 comments
Assignees
Labels
Milestone

Comments

@banister
Copy link
Member

Now we have a lot of plugins available it's become important for the user to manage them properly from within pry. This functionality could be provided by one command or a suite of commands, but the minimum functionality should be:

  • List which plugins are installed
  • List which plugins are active.
  • View a list of all available plugins on rubygems, with descriptions, and their dependencies
  • Possibly install new plugins
  • Possibly uninstall plugins
  • Possibly disable active plugins
  • Possibly enable deactivated plugins

If we want to allow enabling/disabling plugins, it is important we refactor the plugin system and provide it with a few hooks and a way of defining plugin functionality so that they can be activated/deactivated on demand.

Further, this would allow for the proper treatment of plugins like pry-nav which monkeypatch pry core methods

@ghost ghost assigned kyrylo Jul 23, 2012
@kyrylo
Copy link
Member

kyrylo commented Aug 14, 2012

Possible duplication: #348

@kyrylo
Copy link
Member

kyrylo commented Aug 24, 2012

A marked in bold entry indicates that it has been implemented:

  • List which plugins are installed
  • List which plugins are active.
  • View a list of all available plugins on rubygems, with descriptions, and their dependencies
  • Possibly install new plugins
  • Possibly uninstall plugins
  • Possibly disable active plugins
  • Possibly enable deactivated plugins

Currently, I'm waiting for Ryan's (@rf-) refactoring of tests to be merged with master. I haven't added any single test on my branch for this new functionality: I just don't want to resolve a ton of merge conflicts in the end.

@banister
Copy link
Member Author

also see: #348

@rf-
Copy link
Member

rf- commented Apr 29, 2014

Closing this in favor of #699

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

No branches or pull requests

3 participants