grammar-guard.nvim VS nvim-highlite

Neat post! I like to throw in angry-reviewer and grammar-guard.

Something like grammar-guard, proselint and/or language-tool?

Hi, it seems that the ltex-ls will not have this features added https://github.com/neovim/nvim-lspconfig/issues/1443, but there is no plugin available to do it, grammar-guard has stalled.

I am actually writing a blog post on almost this exact topic! Ltex-ls https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md#ltex is not fully integrated yet, add to dictionary doesn't do anything! You can add manually for now in the setup, for example: lua require('lspconfig').ltex.setup { settings = { ltex = { disabledRules = { ['en-US'] = { 'PROFANITY' } }, dictionary = { ['en-US'] = { 'Deno', 'Neovim', 'ltex-ls' } }, }, }, } The above disables a rule, and adds some words to the dictionary. Adding these rules manually is not ideal, but using ltex-ls in Neovim is new and the ability to do these things automatically has not yet been added. Keep an eye on grammar-guard.nvim for these features being added.

I made a plugin that checks your grammar while you're writing LaTeX or Markdown Documents!

nivm-highlite boasts ease of configuration, but I haven't tried it yet. It shows only dark themes, but most of the themes support `background=light`. However they are kinda low contrast out of the box.

My plugin and mini.colors can also do it.

tl;dr: export your favorite themes to new formats (e.g. wezterm theme), generate new colorschemes from only a palette of colors, update old colorschemes to automatically include support for new plugins (it sometimes makes them faster too). Repo link

Wow. I just spent like an hour the other day converting colortrans to Lua because I wanted my colorscheme generator to work with all systems, but with this I can just remove built-in support for cterm and suggest mini.color for that purpose.

Mine, nvim-highlite

I do wish there was a builtin way to partially link highlight groups. In my colorscheme I opted for this syntax, which resolves self into the batch of groups being defined recursively unwraps highlight links to fetch the true highlight group being referenced.

Shameless self-plug, but nvim-highlite and all of its inheritors support everything from 8-bit to 256-bt and is written using the Neovim API.

Haven't tried newer color schemes on the block, but I have tried a lot and all of them add 100s of ms to startup time. Eventually settled on a copy of https://github.com/Iron-E/nvim-highlite. Another culprit tends to be all the fancy statusline.

Not to self advertise (regulars here know I do that enough), but my colorscheme is made to work in any range of color. If you don't like it, look under the usage section— all of the colorschemes others have made with it also work without termguicolors.

I'm a little puzzled as to why they'd do that. It's completely possible to use the :colorscheme command.