* fix(treesitter): highlight wildcards in .gitignore differently
* fix(treesitter): color paths in `.gitignore` as mauve
* fix(treesitter): color paths in `.gitignore` as text
* Add lazy.nvim plugin updates in feline
* Use pcall for checking if lazy.nvim is installed
* fix(feline): fix provider option for lazy updates
* refactor(feline): update deprecated api functions
* feat(native_lsp): support new "Ok" diagnostics
Defaults to using the green color.
This was not added to the "LspDiagnostic*" highlights since I could not
find any documentation on whether the "Ok" diagnostic is implemented for
those. Indeed, I could not find any documentation whatsoever on the
LspDiagnostic* highlights (grepping the Neovim source turned up no
mentions of them either).
* doc(native_lsp): new "Ok" diagnostic
Add documentation and type information for the new "Ok" diagnostic.
* feat: add diffview integrations
* chore: fix docs
Documentation should have same value as in `init.lua` defaults :)
* refactor: remove linked highlight
---------
Co-authored-by: mrtnvgr <root@unixis.fun>
* feat(treesitter): follow upstream captures
This PR primarily updated highlight groups related to treesitter captures to
comply with the updated specification. Deprecated captures were relocated to the
legacy section. All changes are based on the following four commits:
- 99ddf57353
- 5d75359a9a
- dccf31f9b1
- 998b230a77
I've attempted to keep the colors consistent for new additions by looking at the
definitions of existing captures, but I'm _really_ not sure how to handle colors
for documentation-related ones. AFAIU the only relevant existing capture is
`@markup.raw`, but it seems better suited for smaller sections of documentation.
Personally, I don't think a large block of greenish-blue would look great for
extensive documents that might span multiple lines.
Signed-off-by: Jint-lzxy <50296129+Jint-lzxy@users.noreply.github.com>
* feat(lsp): add highlight for `LspCodeLensSeparator`
* link `LspCodeLens` with `LspCodeLensSeparator`
---------
Co-authored-by: mrtnvgr <root@unixis.fun>
* fix: Background color Airline section B.
Airline section B is used to show information regarding vcs, i.e. git
branch. This section was formatted the same as section C, so they were
indistinguishable.
This commit changes the bachground color to the same one used for
Lualine.
* fix: Airline warning section in Replace mode
The colors for the error and warning section of Airline were not applied
to replace mode. This commit fixes this issue by instead defining
the replace mode colors as a variation of the insert mode colors, where
these colors are already deifned. Note that the red color is only
applied to Airline sections A & B, but not on the right side, since the
red color is already used there for the error section. This is different
from Lualine, since there the error & warning sections don't exist.
* feat: Add Terminal+Command mode colors to Airline
This adds support for different colors for Airline in terminal mode and
command mode, where before simply the normal mode colors where used.
For terminal mode, its simply a copy of insert mode. This makes sense
since it is basically insert mode just for the terminal buffer. In
Lualine, this is done the same way.
For command mode, it is a variation of normal mode. The orange color is
also used in Lualine for this purpose. Only the sections A & B (on the
left) are modified with this color, different from Lualine. Reason is
the same as for Replace mode; the orange color is already used on the
right for the warning section.
