General.vim: general editor settings like tabstops etc Plugins.d: files containing vim plug plugin install commands and their accompanying configĪutocmd.vim: all my autocmds for changing file type settings etcįuncs.vim: any functions that I need for various shit Im on mobile so forgive the brief explanation. Thank you for your time devoted to this topic. I would appreciate your suggestions in this matter (or some online resources) and, in the end, will be happy to share the outcomes of my learning (planning to start a public dotfiles repo). lazy plugin loading, filetype dependent loading, local function scopes, load guards, the purpose of after or ftplugin directories and many others like the concept of splitting plugin loading into multiple files (some managers allow for that, right?). How do I take into consideration all the different features which Vim and its plugin managers give: e.g. How make my Vim configuration folder easily maintainable and clear to debug if needed? (For instance: I heard that only simple file sourcing of multiple other vim-config files in. What is the order of loading/inlcuding these configuration files into. Is here some general recommended way of doing multi-file vim configuration? (Creating vim-related config files based on: filetype specific organization / purpose specific organization (coding, writing papers) or other ways to divide?)
vimrc (or init.vim) into multiple files?Ĭould you share your vim-related dotfiles directory structure and elaborate on it a bit? What are your choices and why? What are the does and don'ts of splitting. A novice in this area of Vimming, I would be happy to learn from your experience. I feel that choosing a good approach, like a good "design pattern" which will save a lot of reorganization effort in the future.
I read some initial guidelines and am looking for a way to organize Vim setup better - into multiple files.
Dividing file into sections dedicated to plugin loading, mappings, functions, plugin options is no longer convenient. Thank you for helping out and suggesting so many interesting solutions to the given task! While almost all were a valuable help, I found the responses awarded especially helpful - might be worthwhile for future readers to check them out.
0 kommentar(er)
