Question 1

How do I export a colorscheme to Wezterm using nvim-highlite?

Accepted Answer

Use require('highlite.export').wezterm('colorscheme-name', options) with Neovim 0.9+. Specify options like dir and filename, and consider using build hooks in plugin managers for automatic updates on changes.

Question 2

nvim-highlite vs lush.nvim: which should I choose?

Accepted Answer

nvim-highlite is better for rapid development with minimal color input and broad plugin support, while lush.nvim offers a more declarative, real-time preview approach. Pick based on whether you value ease of creation or detailed customization.

Question 3

How to create a custom colorscheme with nvim-highlite?

Accepted Answer

Define a palette with a few colors in Lua, then use the generator utilities to create highlight groups. Refer to the advanced usage guide for specifics on cloning and extending groups, and ensure setup is called before applying the colorscheme.

Question 4

Does nvim-highlite work without termguicolors?

Accepted Answer

Yes, but you need mini.colors to infer cterm palettes. Use require('mini.colors').get_colorscheme('name'):add_cterm_attributes():apply() or export it once with build hooks for performance, as detailed in the FAQ.

Question 5

What plugins are supported by nvim-highlite?

Accepted Answer

It supports numerous plugins, including Neovim ones like telescope, gitsigns, and Vim ones like coc, nerdtree. Full lists are in the README under Neovim and Vim plugin sections, with options to disable specific integrations.

Question 6

How to override highlight groups in my init.lua?

Accepted Answer

Add an autocmd for the ColorScheme event with a callback using vim.api.nvim_set_hl. Specify patterns like 'highlite' or '*' to target specific colorschemes, and load the colorscheme after setting the autocommand.

nvim-highlite

What is nvim-highlite?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions