We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Expected behavior: yarw copies a remote word
Actual behavior: yarw copies everything between cursor and leap target and autopastes it, despite setting paste_on_remote_yank = false
paste_on_remote_yank = false
I eventually figured out that commenting out my remapping of 'p' to 'v' fixes the issue. Using legendary.nvim:
keymaps = { { 'v', 'p', mode = { 'n' }, opts = { noremap = true } }, },
causes the weird behavior. Took me a while to isolate this one!
Legendary keybinds are set before calling require('leap-spooky').setup()
require('leap-spooky').setup()
Using latest version of leap and leap-spooky, nvim 0.8.3 and 0.9.0 nightly.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Expected behavior: yarw copies a remote word
Actual behavior: yarw copies everything between cursor and leap target and autopastes it, despite setting
paste_on_remote_yank = false
I eventually figured out that commenting out my remapping of 'p' to 'v' fixes the issue. Using legendary.nvim:
causes the weird behavior. Took me a while to isolate this one!
Legendary keybinds are set before calling
require('leap-spooky').setup()
Using latest version of leap and leap-spooky, nvim 0.8.3 and 0.9.0 nightly.
The text was updated successfully, but these errors were encountered: