User autocommands broken after commit 00ed2f1

[clason]

Description

The latest commit 00ed2f1 broke user autocommands; specifically the line

vimtex/syntax/tex.vim

Line 43 in 00ed2f1

autocmd User <buffer> VimtexEventInitPost call vimtex#syntax#core#init_post()

(removing the <buffer> avoids the error).

Steps to reproduce

Use the following mini.vim (to avoid interference from installed packages):

let rtp = $VIMRUNTIME
let packpath = $VIMRUNTIME .. '/site'
set nocompatible
let &runtimepath  = '~/.local/share/nvim/site/pack/packer/start/vimtex,' . &runtimepath
let &runtimepath .= ',~/.local/share/nvim/site/pack/packer/start/vimtex/after'
filetype plugin indent on
syntax enable

1. nvim --clean -u min.vim test.tex
2. :doautocmd User Foo

(These steps are pointless but minimal; they reproduce similar errors from the builtin LSP client and Telescope when opening tex buffers, for example.)

Actual behavior

Error detected while processing User Autocommands for "<buffer=1>":
E492: Not an editor command: VimtexEventInitPost call vimtex#syntax#core#init_post()

VimtexInfo

Vim version: NVIM v0.6.0-dev+249-g086631cd9

[storopoli]

I can confirm that it broke both my mac nvim and linux nvim.

[mathjiajia]

My UltiSinps is broken after this update.
After rolling back to vimtex-2.6, everything becomes fine.

[clason]

Fixed indeed, thank you!

[lervag]

Fixed now. I'm sorry for introducing the bug just before releasing v2.7. But I believe most people more or less follow the latest version from github.

[clason]

Probably want to cut a quick v2.7.1 nevertheless?

[lervag]

Fixed indeed, thank you!

Thanks for providing the useful and to the point issue description; and for noticing and reporting immediately!

[lervag]

Probably want to cut a quick v2.7.1 nevertheless?

Done.