The ftdetect script for .votl files that comes with this plugin is currently nested inside an augroup filetypedetect ... augroup END block:

As this comment on another plugin's issue tracker points out, there is no need to do this, as Vim already opens an augroup filetypedetect context before running ftdetect scripts.

But doing so in your own ftdetect script is not just useless, it's actually harmful to other ftdetect scripts that do rely on being run inside of an augroup filetypedetect context: By leaving this context at the end of your script, you stop all those scripts from working properly, as happened in hashivim/vim-terraform#179.

It's worth pointing out that out of the many plugins I have installed, vimoutliner is the only one that does this:

$ find . -path '*/ftdetect/*.vim'
./vimoutliner/ftdetect/votl.vim
./vimtex/ftdetect/cls.vim
./vimtex/ftdetect/tikz.vim
./vimtex/ftdetect/tex.vim
./unicode.vim/ftdetect/unicode.vim
./quantum_espresso-vim/ftdetect/espresso.vim
./vim-terraform/ftdetect/hcl.vim
./vim-graphql/ftdetect/graphql.vim
./vim-fugitive/ftdetect/fugitive.vim
./vim-maktaba/vroom/fakeplugins/ftplugin/ftdetect/newtype.vim
./vim-hcl/ftdetect/hcl.vim
$ rg 'augroup' $(find . -path '*/ftdetect/*.vim')
./vimoutliner/ftdetect/votl.vim
22:augroup filetypedetect
25:augroup END

I don't know if you introduced this as a defensive measure against another popular script doing the same thing (and hence messing it up for other scripts including vimoutliner), but if so, then it would probably be better to just specify the filetypedetect group explicitly for every single autocmd command or to not leave the augroup context at the end of the script.

Objections / thoughts?