Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Neovim 0.10 updates #936

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Neovim 0.10 updates #936

wants to merge 4 commits into from

Conversation

VlaDexa
Copy link
Contributor

@VlaDexa VlaDexa commented May 16, 2024

This is a PR that cleans up the config in accordance to new stable features.

I have made the following changes:
Key Mappings:

  • Remove K, [d and ]d mappings, since they are included by default
  • Remove <leader>e mapping, because neovim started using <C-W>d for this by default

Plugin changes:

  • Remove Comment.nvim, since neovim now includes their commenting tool (see :help commenting)

Chores:

  • There is a new recommended way of checking for LSP capabilities, so change to that
  • Remove check for vim.lsp.inlay_hint presence, since stable now supports it

Fixes:

  • Fix problems with the default parameter of the buffer of vim.lsp.inlay_hint.is_enabled

Accumulated PRs

@VlaDexa
Copy link
Contributor Author

VlaDexa commented May 16, 2024

I should add that this probably shouldn't be merged too soon, since 0.10 released today, and it's probably not in many repos. But, I think these changes are fit to be in the main, since the point of kickstart is to be small and support the latest stable Neovim, and not provide a backwards compatible config that works everywhere.

@dam9000
Copy link
Contributor

dam9000 commented May 16, 2024

I think merging this should be delayed by a couple of months, since it will take a while for all the distributions and package managers to upgrade to the latest 0.10 release. In the meantime, the kickstart config as is works perfectly fine also on 0.10. Merging this does not fix anything but it will break functionality for people still on 0.9.5.

@dam9000
Copy link
Contributor

dam9000 commented May 16, 2024

In addition, if these changes are integrated then the :chekhealth would also need to be updated to require minimum version to be 0.10.0 instead of the current 0.9.4 - see lua/kickstart/health.lua

Alternatively these changes could be made conditional with something like:

if vim.fn.has 'nvim-0.10' == 1 then
...
end

curiously, the below version check does not work for me in nvim 0.10:

if vim.version.ge(vim.version(), '0.10') then
...
end

any idea why? I tested it with the prebuild nvim-linux64.tar.gz 0.10 release.

@VlaDexa
Copy link
Contributor Author

VlaDexa commented May 16, 2024

prebuild nvim-linux64.tar.gz 0.10 release

Check your vim.version(). Just downloaded the release files from github, and it seems that they have packaged a version with a dev mark on it. Their version comparator looks for that and if it finds some prerelease mark it shows that 0.10-dev is greater than 0.9 but still less than 0.10

@dam9000
Copy link
Contributor

dam9000 commented May 16, 2024

@VlaDexa you are right, vim.version() says:
0.10.0-dev+g27fb62988

init.lua Outdated Show resolved Hide resolved
Provide the buffer for which to enable inlay hints

Co-authored-by: Matt Mirus <matt@mattmirus.com>
@blarz
Copy link

blarz commented May 24, 2024

Regarding the delay merging the PR, the README says:

Kickstart.nvim targets only the latest 'stable' and latest 'nightly' of Neovim.

So it would make sense to merge this now or soonish IMHO.

At which point do you declare it ready to go, when you say we should wait for distributions to package it?

But I also see this point:

Merging this does not fix anything but it will break functionality for people still on 0.9.5.

How was this handled during the 0.9 release?

monrad added a commit to monrad/dotfiles that referenced this pull request May 26, 2024
@VlaDexa
Copy link
Contributor Author

VlaDexa commented Jun 5, 2024

Can I collect here commits from other PR's that also suggest stuff for neovim 0.10? I think GitHub will autoclose those ones if this big PR containing their commits get merged
I'm talking about #961 and #956, for example

@VlaDexa
Copy link
Contributor Author

VlaDexa commented Jun 8, 2024

Got tired of waiting for someone to reply. If anyone wants for these commits from other PR's to not be included here please tell me.
For PR authors whose commits I merge here: please don't close your requests, as inclusion here doesn't mean it will get merged upstream

MarinJuricev added a commit to MarinJuricev/kickstart.nvim that referenced this pull request Jun 15, 2024
@rmacklin
Copy link
Contributor

rmacklin commented Jun 20, 2024

I think GitHub will autoclose those ones if this big PR containing their commits get merged

That would only happen if 1) you did a merge of #961 rather than a cherry-pick (as it stands now, only #956 could be auto-closed, since that PR's exact history is included in this branch's history) and 2) this PR was merged using a merge commit rather than a squash-merge - but the maintainers normally do a squash-merge so... 🤷‍♂️

Edit: You inspired me to add some more reasons to https://github.com/rmacklin/why_i_dont_recommend_squash_and_merge

@rivenirvana
Copy link

Are these going to be merged anytime soon?

@VlaDexa
Copy link
Contributor Author

VlaDexa commented Jun 30, 2024

Fixes #992

11Firefox11 added a commit to 11Firefox11/.dotfiles that referenced this pull request Jul 1, 2024
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.

None yet

10 participants