You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Like the title states, I'm getting No matching autocommands: UsetUltestPositionsUpdate in the status line.
To Reproduce
Steps to reproduce the behavior:
Run UltestStop or UltestStopNearest. The message appears whether or not any tests are currently running.
Expected behavior
No message claiming there aren't any auto-commands. I don't particularly care, and there are ways to check this for debugging purposes if I did care.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
This happens even if I remove all my vim-test & vim-ultest configuration from my vimrc. If you need my entire vimrc or you think any part of it could be causing this, or if you need any other info, please ask and I'll provide it if I can.
I'm using vim. The version is 8.2, with patches 1-3450. Not sure if this is the latest, but it's pretty darn recent.
The text was updated successfully, but these errors were encountered:
Describe the bug
Like the title states, I'm getting
No matching autocommands: UsetUltestPositionsUpdate
in the status line.To Reproduce
Steps to reproduce the behavior:
Run
UltestStop
orUltestStopNearest
. The message appears whether or not any tests are currently running.Expected behavior
No message claiming there aren't any auto-commands. I don't particularly care, and there are ways to check this for debugging purposes if I did care.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
This happens even if I remove all my
vim-test
&vim-ultest
configuration from myvimrc
. If you need my entirevimrc
or you think any part of it could be causing this, or if you need any other info, please ask and I'll provide it if I can.I'm using
vim
. The version is 8.2, with patches 1-3450. Not sure if this is the latest, but it's pretty darn recent.The text was updated successfully, but these errors were encountered: