Skip to content

Fix typo: compeletions#28

Closed
diegorodriguezv wants to merge 47 commits intooriori1703:maintained-upstreamfrom
diegorodriguezv:mine/typo2
Closed

Fix typo: compeletions#28
diegorodriguezv wants to merge 47 commits intooriori1703:maintained-upstreamfrom
diegorodriguezv:mine/typo2

Conversation

@diegorodriguezv
Copy link
Copy Markdown

Fix typo: compeletions

5brian and others added 30 commits April 11, 2025 23:43
Guide users towards lazy's `init` key for plugins written in VimScript.
Add lua_ls annotations for improved hover experience and replace vim.fn.empty() with
vim.tbl_isempty()
The following lines do nothing and can be removed:

 format = function(diagnostic)
   local diagnostic_message = {
     [vim.diagnostic.severity.ERROR] = diagnostic.message,
     [vim.diagnostic.severity.WARN] = diagnostic.message,
     [vim.diagnostic.severity.INFO] = diagnostic.message,
     [vim.diagnostic.severity.HINT] = diagnostic.message,
   }
   return diagnostic_message[diagnostic.severity]
 end,

The following line causes diagnostics which aren't of severity level
error to not have the specific text area underlined. This is less useful
than the default of showing underlines for all diagnostic levels, so
remove this line as well:

  underline = { severity = vim.diagnostic.severity.ERROR },
This would allow to write more concise and easy to understands keybinds in
the following commit
This could help beginners to get autocompletion, catch mistakes earlier,
and allow them to skip the docs for simple configs.

This is not perfect because a lot of the plugins type all of their keys
as required, even though they have defaults, but this is good enough.
feat(diagnostics): Add `virtual_lines` for discoverability
feat(grep-string): works with visual selection too
…stic-config

fix(diagnostic): remove unnecessary config lines
feat: add toggle to show/hide diagnostics
Add type hints to plugin options where possible
feat: Enhances breakpoint editing

The keymapping `<leader>B` is now configured to guide users through the
process of adding a `condition`, `hitCondition`, and `logMessage` to a
breakpoint.

---------

Co-authored-by: Brian Lehrer <661570+blehrer@users.noreply.github.com>
docs: Add documentation for lazy's `init` key
docs: Document methods to get the latest neovim
…on-maintained-upstream

Raise the minimum nvim version to 0.11
cameroncc and others added 17 commits July 11, 2025 23:08
Adds 'gr' to which-keys documentation, so users can see that LSP actions are grouped after 'gr' key binds.

It used to be directly under 'g', which required no additional grouping info on which-keys. See nvim-lua#1427 for further explanation on the key binds change.
fix: adjust after 'mini.nvim' transfer to 'nvim-mini' org
Fixed a bug in blink.cmp causing editor freezes on WSL2 systems
@oriori1703
Copy link
Copy Markdown
Owner

I'm now a maintainer of the upstream kickstart.nvim, so you should probably change your remote to that repo :)

@oriori1703 oriori1703 closed this Feb 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.