Skip to content

Conversation

Jint-lzxy
Copy link
Collaborator

Neodim's recent updates (specifically zbirenbaum/neodim@2ac2f25) introduced/utilized some of nvim 0.10's APIs, which might be a source of trouble for nvim 0.9.*, so IMO we'd better pin neodim to v2.0 to avoid potential issues :D

Neodim's recent updates introduced/utilized some of `nvim 0.10`'s APIs,
which might be a source of trouble for nvim 0.9.*, so IMO we'd better
pin `neodim` to v2.0 to avoid potential issues :D
Copy link
Collaborator

@CharlesChiuGit CharlesChiuGit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

agreed

@ayamir ayamir merged commit f9ad3d7 into ayamir:main Sep 21, 2023
@Jint-lzxy Jint-lzxy deleted the fix/pin-neodim-version branch September 21, 2023 11:53
singlemancombat pushed a commit to singlemancombat/nvim-config that referenced this pull request Sep 30, 2023
Neodim's recent updates introduced/utilized some of `nvim 0.10`'s APIs,
which might be a source of trouble for nvim 0.9.*, so IMO we'd better
pin `neodim` to v2.0 to avoid potential issues :D
@ayamir ayamir mentioned this pull request Oct 18, 2023
3 tasks
@ayamir ayamir mentioned this pull request Jan 8, 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.

3 participants