Vroom is using settings in ftplugin/ directory

[nfischer]

Although vroom behavior isn't affected by .vimrc configurations, it looks it can be affected by personal configuration lying under ~/.vim, such as ~/.vim/ftplugin. This is a big concern when testing things like filetype plugins, but it could potentially raise an issue for any sort of plugin (ex. I'm unintentionally depending on a script in .vim/autoload).

This doesn't seem to be vroom-specific, since vim -u NONE still includes ~/.vim in the rtp. However since this has a big impact on vroom, is there any way vroom can step around this vim behavior? If not, maybe there should be some sort of warning in the README.

[dbarnett]

Forcing $HOME to a throwaway temp dir would fix that, if vim doesn't have a mechanism more robust than -u NONE.

[dbarnett]

Found the StackExchange question for it: http://vi.stackexchange.com/questions/6112/how-can-i-get-vim-to-ignore-all-user-configuration-as-if-it-were-freshly-instal
The only viable answer there is $HOME.

[nfischer]

The temp directory approach listed there might be a good option, if vroom is able to create it and clean it up.

[dbarnett]

Found there's a better solution now on that StackExchange link: vim has a --clean flag to do a better job of bypassing local configs (in vim 8.0.1554+ and neovim 0.4.0+). That'd be perfect to use in vroom, but we'd still probably want to detect the argument failure on older vim versions and run without it.

[dbarnett]

We should keep this open until we do something about the neovim case, though.