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

How to enable all/safe set of plugins? #14

Open
e3krisztian opened this issue Dec 16, 2017 · 2 comments
Open

How to enable all/safe set of plugins? #14

e3krisztian opened this issue Dec 16, 2017 · 2 comments

Comments

@e3krisztian
Copy link

When starting eye I got a plain window, with a single menu File.
It was a too simple window, I was definitely missing the plugins.

Reading the README again, it says that something has to be done (tried copying files, was not the solution), reading into the docs directory (git grep -i plugins), I was finally able to enable the syntax highlighter.

It would be nice if there would be an easy shortcut to enable a safe set of plugins (or all) without reading into the python sources (git grep -e 'setEnabled(' -e @disabled -e 'install(' -A 2).

@hydrargyrum
Copy link
Owner

When starting eye I got a plain window, with a single menu File.
It was a too simple window, I was definitely missing the plugins.

My first idea was to let it entirely configurable. But you're right, the first contact with this editor is probably a bit too harsh.

I was thinking about having some example config files and letting users copy them, but your idea of a shortcut is even better (though not incompatible with giving sample config files).

What would you think of a menu entry (which could be more visible to the user just starting the editor without having to read docs) that would enable this safe set of plugins (or that would copy a sample config to user directory and enable it immediately)?

Thanks for your input, it's very valuable!
BTW, do not hesitate to come by #eye on freenode irc.

@e3krisztian
Copy link
Author

This issue is in fact two

  • empty config at first startup
  • it is unclear how to enable further existing plugins, I glanced into some and saw setEnabled, install and @disabled as potentially interesting places, example config file for each plugin would help here

Instead of the menu, I think I would go with copying a default config at first start up (= no config directory), which would contain some code to load that config file in the editor and instructions in comments on how to enable other plugins, or where to copy example configs from. This would result in a non-empty window on first startup and remind the user to customize away the default configuration.

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