-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
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
Mini.jump bug: t skips matches at first column #113
Comments
Thanks for the issue! This is by design, as All search logic is done with built-in As a side note: outcome of this use case is a little bit more complex than "put cursor at end of line 2". In Normal mode - yes, in Visual and Operator-pending - probably more reasonable would be to put one line to the right (on "new line character") to allow decreasing line count. Which is another complexity factor. |
Thank you for the response! |
Thanks for the issue! It should be primarily solved on latest Not without some issues (like with |
I have been testing it the past hour or two. It works like a charm 👍 |
Contributing guidelines
Module(s)
Mini.jump
Description
In the below example file, when hitting t) on the second line, I would intuitively expect the cursor to move to he last character in line 2 as the next occurence of ) is the first char of line 3. However the cursor moves to the space before ) on line 5
Neovim version
0.7.2
Steps to reproduce
2Gt)
Expected behavior
Put cursor at end of line 2
Actual behavior
Put cursor before the next match that is not on first column
The text was updated successfully, but these errors were encountered: