Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The diff appears to be large, but the changes are fairly trivial. For reference, here's a quick summary of the changes:
CHANGELOG.md
(reduced indent from 3 to 2 spaces, reworded a couple things, fixed the URLs at the end of the file which were invalid comparisons/revision ranges)CHANGELOG
entry for this release. I decided on a minor release instead of patch release as there are several bug fixes and changes sincev1.0.2
, and also because of all of the highlight group changes made upstream.-
with real unicode bullet points, fixed-up indenting and alignment (aligned elements to 80 chars according to the current modeline, tags should be right-aligned and either on the same line as the title/heading or the very next one up), improved the sections (e.g. added--------
section delimiters). I also added an entry to this changelog as well which covers all of the new and renamed hl groups as of nvimv0.10
(since the beginning of this year, 2024).config.lua
(which are also/mainly used for the argument tosetup()
in order to provide LSP completion for users as well as help catch invalid keys/assignments/values in user config).Note
I applied the class definitions in
config.lua
directly to thedefaults
table literal for a few reasons. One, it seems to improve the type-checking ofdefaults
(because lua-ls is weird), particularly when it comes to the table literals nested withindefaults
(in comparison to just using---@type SomeClassName
on thedefaults
table). Two, it keeps the types/classes close-by when modifying the defaults themselves (i.e. the values) (e.g. you'll usually want to update both at the same time and keep them in-sync). On the other hand, doing it this way does make the file somewhat uglier and harder to read, but it's manageable.