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
{{ message }}
This repository was archived by the owner on Aug 15, 2026. It is now read-only.
Repository navigation
<
8000
link rel="modulepreload" href="https://github.githubassets.com/assets/en-b91ae1bc8ac485d3.js" crossorigin="anonymous" />
This repository was archived by the owner on Aug 15, 2026. It is now read-only.
Vroom should fail on any unexpected ErrorMsg-highlighted messages #55
Vroom's default message strictness setting is GUESS-ERRORS, which uses heuristics to detect messages that look like errors (lines starting with E\d+, ERR, "Error detected while processing", etc). Instead, this mode should fail whenever it encounters a message echoed using the bright red ErrorMsg highlight group.
We haven't been able to do this so far because vimscript doesn't offer any way to programmatically query the highlighting for echoed messages, only the text, but using a libexpect-based runner (#41) might allow us to revisit this.
The heuristics get confusing while working on a plugin that catches and prints red highlighted error messages for errors in user commands, since you'll encounter errors but vroom will just report that the command didn't work without mentioning that there was an error message. Actually, we should probably just always include unexpected messages in the output for other types of errors (syscall expectations, buffer content checks, etc.).
Activity
dbarnett commentedon Oct 1, 2014
The heuristics get confusing while working on a plugin that catches and prints red highlighted error messages for errors in user commands, since you'll encounter errors but vroom will just report that the command didn't work without mentioning that there was an error message. Actually, we should probably just always include unexpected messages in the output for other types of errors (syscall expectations, buffer content checks, etc.).