Question 1

How do I disable a specific language in vim-polyglot?

Accepted Answer

Set the g:polyglot_disabled variable in your .vimrc before the plugin loads, e.g., 'let g:polyglot_disabled = ['markdown']'. You can disable just the plugin part by appending '.plugin', like 'markdown.plugin'.

Question 2

Vim-polyglot vs individual language plugins: which is better for performance?

Accepted Answer

Vim-polyglot is better for performance due to lazy loading and optimized ftdetect, adding only 10ms to startup. Individual plugins might load faster per language but can slow Vim down if many are installed without on-demand loading.

Question 3

Does vim-polyglot work with Neovim?

Accepted Answer

Yes, vim-polyglot is compatible with both Vim and Neovim. Installation is similar using package managers like Plug or Vim's built-in package manager, and it supports Neovim's runtime paths without issues.

Question 4

How to update vim-polyglot manually without waiting for releases?

Accepted Answer

Run 'make' in the plugin directory to regenerate scripts and update language packs. Alternatively, use your package manager to pull the latest changes from GitHub, but note that updates are bundled in releases for consistency.

Question 5

What happens if I already have syntax plugins installed?

Accepted Answer

Vim-polyglot may conflict with existing plugins. Disable specific languages in vim-polyglot using g:polyglot_disabled to prioritize your preferred plugins, ensuring they load correctly without duplicates.

Question 6

How does vim-polyglot handle indentation for new filetypes?

Accepted Answer

It uses an optimized vim-sleuth integration to automatically detect indentation based on file content. If it fails, you can disable this feature via g:polyglot_disabled and set indentation manually or with another plugin.

vim-polyglot

What is vim-polyglot?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions