Neovim/Vim invocation fixes #90
Open
Conversation
This file contains 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
Prevent content sent without final line feed being returned with one. Multi-byte character support for setting cursor position.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add
set nofixeoloption command. Without it, these editors will return content with a line feed character at the end of text, when it was sent without one. Content sent with a final LF will be unaffected.Change
cursor()which works on bytes, tosetcursorcharpos()which is equivalent but works correctly on multi-byte characters. Verify with the string🌲🌲🌲⛳in a textarea and the cursor on the green. The former function will put you in the woods.