On Wed, Jul 27, 2016 at 7:47 PM, Gary Johnson <garyj...@spocom.com> wrote: > On 2016-07-27, Manuel Ortega wrote: >> On Wed, Jul 27, 2016 at 12:26 PM, Gary Johnson wrote: >> >> On 2016-07-27, Manuel Ortega wrote: >> >> > 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. >> >> From ":help VimEnter", the VimEnter event occurs 'After doing all >> the startup stuff, including loading .vimrc files, executing the >> "-c cmd" arguments, creating all windows and loading the buffers in >> them.' >> >> Enabling filetype detection after buffers are loaded is too late. >> >> >> Filetype *detection* is on by default in Vim. It's not being "turned on" by >> "filetype plugin indent on". So what you say will be too late is not too >> late. > > What makes you think filetype detection is on by default? That's > not what I observe. > > $ vim -N -u /dev/null hello.c > :set ft? > filetype= > > It is turned on by "filetype [args] on" and by "syntax on". > > Regards, > Gary
Indeed: filetype detection is turned on by the vimrc_example.vim, but it is neither the 'compatible' nor the 'nocompatible' default in the absence of startup scripts (i.e. neither "vim -u NONE" nor "vim -u NONE -N" have it. Even "vim -u NORC -N" i.e., no vimrc but with global plugins and 'nocompatible' doesn't set it.) To get a reproducible setup with filetype detection, you might want to do something like vim -u /usr/local/share/vim/vim74/vimrc_example.vim (no need to use -N in this case because the vimrc_example.vim sets it.) Best regards, Tony. -- -- 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.
