This repository has been archived by the owner on Apr 16, 2024. It is now read-only.
What direction should doom take? #103
NTBBloodbath
started this conversation in
Ideas
Replies: 1 comment 3 replies
-
I feel like this is a bit above my level so my question might not make sense but wouldn't it work to combine the two options because both sound interesting |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey, as will be known, doom seeks to have great extensibility so that it is not just a preconfigured setup, but also that you can configure it and adapt it to your needs, and that is very good.
However, I want to introduce a new design pattern that allows us to differentiate ourselves even more from the other setups; for this we currently have 2 options (and there may be more, feel comfortable to add another).
For the option 1 we could pin each plugin to a specific commit hash in packer. In that way we can keep the plugins in a certain state / version, and pin them to a new version each doom-nvim release and fix the breaking changes if there are.
For the option 2 we will make doom even more modular, e.g. separate all the keybindings into different modules (e.g. one module for the windows management binds, other for the core, ect). And dynamically call them by using a Lua table in the configurations, like this
and so on with all the stuff that can be more modular, note that the provided example is just a prototype concept and is subject to changes.
Please let me know here what do you think about and what design should be better for us, thanks in advance.
Regards
Beta Was this translation helpful? Give feedback.
All reactions