Fix neovim_sticky strategy use_existing flag #874
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
codeinabox
approved these changes
Dec 1, 2025
Collaborator
codeinabox
left a comment
There was a problem hiding this comment.
Well spotted and thank you!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Neovim deprecated
b:terminal_job_idin version 0.9: https://neovim.io/doc/user/deprecated.html#b%3Aterminal_job_idIt appears to have been removed by 0.10. This causes the
g:test#neovim_sticky#use_existingflag to stop working (produced in 0.11). This replaces theterminal_job_idwith the recommended&channellookup, and replaces the initial buffer lookup to find a buffer name includingterm://.Make sure these boxes are checked before submitting your pull request: (none applicable here, bug fix on strategy only)
doc/test.txt