Neovim verbose level for autocommand debugging

Which `:verbose` level shows autocommand execution without excessive noise?

25.5K reputation · 06 Dec 2021, 23:26 UTC

97K views0

When troubleshooting a plugin that fails to load, I want to see which autocommands are executed during startup without overwhelming the terminal with every internal command.

The `:verbose` command accepts levels 0‑15, but the documentation does not specify exactly which level begins to show autocommand events while keeping the output manageable for a typical init file.

Which verbose level provides the needed detail, and can I limit the output to only autocommand related messages?

1,980 following

Keep exploring this topic

Neovim Core ↔ Lua Runtime: Synchronization of Terminal Output

Investigating whether Neovim’s core should expose a non‑blocking terminal API to Lua, to prevent stalls caused by high‑frequency terminal output.

Which severity threshold should trigger email alerts in DRF exception handling?

Uncertain which severity levels in a DRF custom exception handler should trigger email alerts. Need to balance critical errors against noise, considering status codes, exception types, and dynamic thresholds.

Symfony Monolog fingers_crossed: keeping pre-error debug records from a failed deployment run

Configuring Symfony's Monolog fingers_crossed handler so failed deployments retain their buffered debug and info records, without flooding production logs during normal traffic.

E_DEPRECATED noise in production error_log

Exploring the optimal configuration for error_reporting to balance E_DEPRECATED visibility with log noise reduction in PHP production environments.

Which `:verbose` level shows autocommand execution without excessive noise?

0 answers

Your perspective belongs here.

0 question comments