Home

FAQ

How to find the reason why denops.vim does not work?

First, check the result of :messages command. Most of messages should be recorded in message history.

Next, run health check by checkhealth command in Neovim or CheckHealth command in Vim with rhysd/vim-healthcheck like

Neovim

denops: health#denops#check
========================================================================
  - INFO: Supported Deno version: `1.28.0`
  - INFO: Detected Deno version: `1.26.2`
  - ERROR: Unsupported Deno version is detected. You need to upgrade it to `1.28.0` or later.
  - INFO: Supported Neovim version: `0.8.0`
  - INFO: Detected Neovim version: `0.8.2`
  - OK: Neovim version check: passed
  - INFO: Denops status: `stopped`
  - ERROR: Denops is stopped. Execute `:message` command to find reasons.

Vim with rhysd/vim-healthcheck

denops: health#denops#check
========================================================================
  - INFO: Supported Deno version: `1.28.0`
  - INFO: Detected Deno version: `1.26.2`
  - ERROR: Unsupported Deno version is detected. You need to upgrade it to `1.28.0` or later.
  - INFO: Supported Vim version: `9.0.0472`
  - INFO: Detected Vim version: `9.0.1151`
  - OK: Vim version check: passed
  - INFO: Denops status: `stopped`
  - ERROR: Denops is stopped. Execute `:message` command to find reasons.

Why are plugins that use denops.vim (ddc.vim, ddu.vim, etc.) slow to start on Windows?

Antivirus software may be the cause. Excluding the deno cache directory ("%LOCALAPPDATA%\deno") from the scan may improve the problem.