fast-cursor-move.nvim
fast-cursor-move.nvim copied to clipboard
FEAT: Smooth out Accel. curve, add vim.keymap.set opts & Types
Feature Enhancement of Acceleration Curve and Addition of Keybindings and Types
Summary:
Enhancements to the plugin focusing on improving the acceleration curve for smoother cursor movements, with the potential for adding customizable keybindings (For people that may need to feed keys in that user alternative setups/maps), and integrating typing's for better development experience and code usability.
Key Changes:
Acceleration Curve refinement:
The acceleration curve for cursor movement has been refined to provide a smoother experience, I noticed the curve would lend jumping further than expected when shifting from stage 2 to 3/4. This adjustment helps in achieving quicker; smoother cursor movements while maintaining a curve that should feel reasonably similar and still natural.
Customizable Keybindings (sort of):
Due to the addition of a defaults table, customizable keybinds could be introduced in the future. Some small changes were made to the vim.keymap.set options, so that remap = true. Not having this on by default caused VsCode to fail in applying the keybinds entirely.
Typing integration:
Typing definitions have been added to the project, open to feedback on better structing(s). Definitions can of course be moved out to a different file as needed/wanted. This inclusion aims to enhance the development process by providing type checking but also aids in maintaining a robust codebase. It aims to provide better code usability, readability and consistency in the codebase.
Testing:
- Testing should be conducted to ensure that the new acceleration curve behaves as expected across different scenarios.
- The keybindings should be tested to ensure that they are correctly applied and function as intended (if/where possible).
- Types work, but may need to be tested or double checked if I've missed something/duplicated entries etc.
Great plugin - Learned a couple of things about Lua's odd syntaxing while making the changes too, open to fixup's/changes. note: I've no direct experience with pulling in or handing opts through to plugins via Nvim/lazy.nvim - Not sure if this is the best way to go about it, but happy to learn.