73452Re: Patch: formatoptions in ftplugins
- Sep 30, 2013On 2013-09-30, David Barnett wrote:
> I've found the built-in ftplugin files are all over the place withI'm sympathetic to the problem, but I think your patch is not going
> respect to handling 'formatoptions'. Some ftplugins don't touch
> it, many clobber useful user preferences. I put together a patch
> that batch-changes the ftplugin files to stop clobbering anything
> that might be a user preference.
The procedure for changing a plugin is to first propose the change
to the plugin's author, whose contact information can be found at
the top of the plugin.
> The 'o' and 'r' options determine whether to automatically insertInteresting. I much prefer having 'r' all the time and never 'o'.
> the comment leader when starting a new line after a comment line.
> I want +o -r everywhere, but most ftplugin files force +croql, so
> I have to fight with them by creating after/ files to force -r
> again. These weren't per-filetype settings and should have been
> left alone. Same for 'l'.
In any case, this is what I've put in my ~/.vimrc (after the
:filetype command) to fix the 'o' problem. No need for a huge
number of tiny after files.
au FileType * setlocal formatoptions-=o
" Override any filetype plugin's attempt
" to set the 'fo' 'o' option.
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+unsubscribe@....
For more options, visit https://groups.google.com/groups/opt_out.
- << Previous post in topic Next post in topic >>