Modified Paste Behavior to keep consistent with native vim - #53
Open
yash-fn wants to merge 4 commits into
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
gitignore #52 docs/tags
new paste behavior mimics native vim (almost. cursor position lost on block pastes)
removed all bindings forcing user to set their own bindings if they want to use plugin. preferable over forcing c and p which can confuse some.
another reason to force manual bindings is that vim-plug seems to load plugin before my bindings are set. so I get double bindings for each command. both before and after plug calls same behavior. removing plugin bindings solves this for me and I see other plugins that decided to force bindings for similar reasons. idk. don't care to keep hacking to find out.