2016-07-28 1:04 GMT+09:00 Manuel Ortega <mannyvim...@gmail.com>: > On Wed, Jul 27, 2016 at 11:40 AM, Manuel Ortega <mannyvim...@gmail.com> > wrote: > >> >>> I agree that "syntax on" and "filetype on" (maybe even "filetype plugin >>> indent on") are pretty core features that should probably be enabled by >>> default, as nearly everyone will use them. >>> >> >> >>> However, I disagree that this should come at the expense of being able >>> to set up specific options. Anything done in the default settings should >>> be modifiable by the user, and it looks like in this situation that is >>> not possible, if the default settings are always sourced. >>> >> >> I would have no problem with "syntax on" going in a system vimrc if it >> didn't have unfixable side-effects. >> >> Perhaps it's possible for Bram to change the behavior of "syntax on" so >> that it doesn't cause menu.vim to be loaded. Same for "filetype on". >> >> Or perhaps it's possible for Bram to change them so that menu.vim isn't >> loaded until after the user's vimrc is loaded. Then the user could at >> least set the "did_install_*" variables. >> >> -Manny >> > > What if "syntax on" and "filetype plugin indent on" were moved into the > autocmd group "vimStartup" that the proposed system vimrc defines, under > VimEnter autocmds: > > au VimEnter * syntax on > au VimEnter * filetype plugin on > > This way, everyone who wants them still gets them, and &go+=M still works > without modification. As an added bonus, both of the "ons" can be > prevented from ever happening using the same "au!" line that kills the > others in that group. >
It may be true that setting go+=M will reduce memory usage and make startup faster. But I would say the benefit gained by doing that is quite marginal. A large amount of memory is to be allocated for the menu, the toolbar, the scrollbar and the icon images in gvim and X11 even if they are to be hidden by guioptions such as cM. And even if those widgets and images are known in advance not to be shown on the screen, a sequence of fairly convoluted calculations for widget geometry is to be done before gvim actually appears on the screen. Hence, in comparison with those heavy tasks, what is gained by go+=M is negligible. I don't understand why go+=M is so important for some people. > -Manny > > -- > -- > 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. > For more options, visit https://groups.google.com/d/optout. > -- -- 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. For more options, visit https://groups.google.com/d/optout.
