A Neovim extension for Leap that enables remote operations on native text objects via atomic motion-selection bundles.
leap-spooky.nvim is a Neovim extension for the Leap motion plugin that enables remote operations on Vim's native text objects. It allows users to perform actions like yanking, deleting, or changing text objects from a distance by combining leaping motions with text object selections into atomic commands, eliminating the need to manually jump to the target location.
Vim/Neovim power users who use the Leap plugin and want to optimize their editing workflow by performing text object operations remotely without disrupting cursor position.
It extends Vim's native text object grammar with minimal new commands, providing intuitive remote operations that reduce keystrokes and enable more fluid editing, especially when working across windows or distant parts of a buffer.
👻 Actions at a distance
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Enables executing commands like yank or delete on text objects without moving the cursor, as shown with examples like `yarw` for yanking a word remotely after a Leap motion.
Allows operating on text objects across different Neovim windows using affixes like 'R' for remote cross-window operations, enhancing multi-window workflows.
Extends Vim's existing text object grammar with minimal new commands, making it intuitive for Vim users, similar to how it mirrors targets.vim-style commands like `cr]`.
Supports remote operations even while in Insert mode, enabling seamless editing without mode switching, as mentioned in the 'fun things' section with `...<C-o>yaRW[leap]...`.
The README explicitly states it's a WIP with 'everything experimental at the moment,' making it prone to breaking changes and unsuitable for stable environments.
Requires the Leap.nvim plugin to function, adding an extra dependency that complicates setup and may not align with minimalist Neovim configurations.
Customization options are noted as 'absolutely not stable API,' limiting advanced users who need reliable and well-documented configuration beyond basic setup.