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.