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

Layer configuration stack into layers of varying opinion. #1

Open
jordwalke opened this issue Mar 17, 2014 · 7 comments
Open

Layer configuration stack into layers of varying opinion. #1

jordwalke opened this issue Mar 17, 2014 · 7 comments

Comments

@jordwalke
Copy link
Owner

  1. baseline configuration (like css reset for vim).
  2. Mac integration (make keymappings consistent with other mac apps).
  3. Generally useful plugins that don't require many keyboard mapping opinions.
  4. Opinionated paradigms such as split/window/tab navigation and keyboard mappings such as "ctrl-l gets you out of everything".

Users should be able to opt out of a particular layer.

@ladislas
Copy link

looking forward to that :)
I really love what you've done and your configuration is great.
But customization is kind of difficult I think.

It would be great to define groups of plugins you could activate or not depending on your current work.
Here is a great example I am using bling/dotvim
the configuration is very granular and well documented so it's really easy to add new plugins, to change the color theme, the fonts and so on.

@jordwalke
Copy link
Owner Author

@tinyladi Yeah, let's do that. Just to start with, just being able to disable entire features one by one would be great - then the ability to customize the keymappings on top of it will come next.

Even though VimBox uses several plugins behind the scenes, I'd rather expose even higher level customizations that we translate to the lower level plugins. (Expose things like g:VimBoxComplete="<Tab>") The reason being that the goal of VimBox is to create a modern editing experience and we'll use whatever plugins/plumbing behind the scenes to get that effect working well. If we find ones that work better, we should swap them out and still have people's high level settings still work well with the new plugins.

@ladislas
Copy link

I totally agree!
So what is your precise roadmap? If I can be of any help, just ask! :)

@jordwalke
Copy link
Owner Author

@tinyladi Let's start with what you would want to customize. Which high level features do you want to toggle on/off (or which key mappings).

@jordwalke
Copy link
Owner Author

Feel free to make a pull request. I'm sure whatever you have in mind is great! Just keep in mind that we should (try to) expose high level settings that don't depend on particular plugins.

@ladislas
Copy link

Okay, I'll take a deep look at it during the weekend.

@jordwalke
Copy link
Owner Author

Feel free to start small with disabling/enabling one plugin etc.

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