-
Notifications
You must be signed in to change notification settings - Fork 26.3k
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
reorganize init.lua to a multi file setup #473
Conversation
Hi there! First off, thanks for your contribution! The beauty of open source is that there's no harm in submitting a PR. As you say, the nature of this particular project is that it's largely a single file. One file to read. One file to understand. Would you consider starting a fork? That way you could maintain whatever organization makes sense for you, and folks can use your fork instead who want a multiple file approach. As always I welcome community input. If folks feel very strongly that a multiple file approach makes more sense, then please chime in here. If enough people feel this way we can re-open and reconsider this PR, but I'm closing it for now. |
@feoh thanks for the feedback. |
This is what makes me find it usable, I've tried to use neovim many times, but only this one helps me dive into the world of neovim. |
@dam9000 That's fantastic! With your approval I'll add a note to the README for folks who might prefer a multi-file approach so they can more easily find your project. |
@feoh Sure, of course I approve and welcome if you can add a link to my multi-file fork to the README. And I'll try to do my best to keep it up to date with all the upstream changes, while making no other functional changes. |
I know that maintaining oss projects is hard so I am here to thank you all for both the single file kickstart, the modular kickstart and the starter as someone new to neovim I find all of them very helpful and a good augmentation for my learning as I get into the weeds appreciate y'all |
This kickstart finally kickstarted my journey into neovim fully. I'd started and stopped so many times, but I'm going fully in now -- I even deleted VSCode to force myself -- and its been going pretty well. |
Just need to modularize the init file now so that I don't have to keep quitting neovim every time I make a change. |
I understand the kickstart init.lua is single-file by design, and most likely this PR will not be accepted and that's fine. I just think a multi-file approach is better, even for beginners. In any case thanks for the kickstart.nvim it is the best starting point for nvim configuration.