Repository navigation
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
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.
Closes #16
handle_hovernow looks up the item under the mouse first and bails out if itshover.idis already the hovered one, so moving inside the same item doesn't redraw anything. Behaviour on entering/leaving an item is the same as before.Numbers
nvzone/menu (default items, 28x12), real TUI in a pty, 1248 mouse moves fed one at a time, 5 runs each:
4351c5c~9.5x less volt work per mouse move, 26x fewer extmark writes. Terminal output is byte-identical (nvim already drops redraws that don't change anything), so this is purely CPU.
Testing
id, none usehover.callbackstylua --check luaAI disclosure: i used Claude to help profile this and write the patch, then reviewed it myself.