-
Notifications
You must be signed in to change notification settings - Fork 47
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
External plugin templates #18
Comments
I do not think these files belong in the core lush project because:
I think they either go into:
I don't think I mind hosting a starter/helper repo, probably mostly just a matter of deciding on a format and writing a readme on what they are and how to use them. |
Maybe they could be added as a submodule to the https://github.com/rktjmp/lush-template. |
Isn't that just including them directly but with extra steps? At any rate. I think they should by default be:
So someone can grab the file and just update whatever parts they need without clearing any existing highlight links setup by the plugins. How/where are you generating these from? |
I think that i order to download the submodules, you have to have write
Sure, that is sensible.
I just grabbed some big colourschemes, concatenated them, sorted them, filtered them and then edited the result with some vim macros. This inherently means, that the list of groups is not necessarily exhaustive... I will make a private repo and invite you. Then, when it gets stable and we figure out the specific layout, we can make it public and figure out where to put it (or if I should transfer ownership to you or something)... |
You can look at the new repo I created. It should work with the new |
Just thinking out loud, the starter template could actually have multiple branches by default
You could probably start main then just merge in what you want What I want to avoid is someone cloning down that repo, seeing 1000 files and thinking Lush is really heavy and complex when it really isn't. |
That seems reasonable. I think that it should also be emphasized in the README that the plugins are really templates and there is no need to implement a lot of them... So the template should then be in one repo not two as we agreed upon before... |
https://gist.github.com/kunzaatko/65c2317018afdbfc69abac9c7737722b
The text was updated successfully, but these errors were encountered: