Forcing defaults.vim to always load is not a good idea. I have used Vim since version 3 . The only time I was really upset by an incompatible change was when version 7.4.xxxx introduced defaults.vim
Ajit On Wednesday, May 29, 2024 at 9:17:55 AM UTC-3 vim-dev ML wrote: > * James McCoy ***@***.***> [240528 15:23]: > > > It might be useful to articulate the "strategy" of Vim in order to > > > provide a clear way to settle such problems. > > > > From my perspective, Vim's strategy _used_ to be to gracefully upgrade > > the user's experience as they became more familiar with Vim. A plain > > Vim install (with no config files) would behave relatively close to > > vi. Create a vimrc (even an empty one) and you would be upgraded to > > Vim defaults. All was good. > > > > Then there was a desire to expose more users improvements that had > > happened in the intervening decade or so and defaults.vim was born. > > However, this _regressed_ the previous behavior of gracefully > > improving behavior. Now, no config files presents the user with "old > > Vim defaults + new settings", which is good. However, as soon as the > > user creates a vimrc they lose the "+ new settings" because > > defaults.vim is no longer sourced. This is a regression in behavior > > from their perspective and they need to figure out how to restore any > > of that behavior they had gotten used to. > > > > Making defaults.vim _always_ apply, with documented ways to revert the > > settings (for things that aren't simply toggling options) would be an > > improvement in the consistency of Vim's behavior. > > While I agree with your sentiment, I am more in line with D. Ben > Knoble's opinion that defaults.vim is really starting to become an > endless bikeshedding exercise. > > I would be very annoyed at having defaults.vim all of a sudden be > sourced the next time I upgrade Vim (or the Debian vim package). I have > already copied the parts I want, and have intentionally left out the > parts I don't want. While I suspect there are plenty of experienced > users who already source defaults.vim in their personal vimrc, I think > most of those who don't would agree with my annoyance. > > :help vimrc points to :help vimrc-intro, which recommends sourcing > defaults.vim. I think most new users who are creating a vimrc for the > first time will find their way to these help topics. I do think it > would be good to update vimtutor Lesson 7.2 to insert between points 1 > and 2 something that points to both help topics. Mentioning > defaults.vim there might also be worthwhile. > > I don't think making defaults.vim always apply is a good idea overall. > > ...Marvin > > — > Reply to this email directly, view it on GitHub > <https://github.com/vim/vim/issues/14853#issuecomment-2137271542>. > > You are receiving this because you are subscribed to this thread.Message > ID: <vim/vim/issues/14853/2137271542 <(213)%20727-1542>@github.com> > -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/7fe9e7f5-7cfc-421a-964a-90098c449c39n%40googlegroups.com.
