Skip to content
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

evil-snipe-skip-leading-whitespace inconsistency #94

Open
bschwehn opened this issue Oct 18, 2023 · 0 comments
Open

evil-snipe-skip-leading-whitespace inconsistency #94

bschwehn opened this issue Oct 18, 2023 · 0 comments
Labels

Comments

@bschwehn
Copy link

bschwehn commented Oct 18, 2023

What did you expect to happen?

This is using doom emacs, which maps t to evil-snipe-t and f to evil-snipe-f.

When I do "vt ", expect visual mode until (exlclusive) next space.
When I do "vf ", expect visual mode until (inlclusive) next space.

What actually happened?

When I do "vt ", visual mode until (inlclusive) next space.
When I do "vf ", expect visual mode until (exlclusive) next space.

Similarly "t " and "f " both do the same thing and go to the next space, when "t " should go to the last char before the space.

Describe your attempts to resolve the issue

Setting evil-snipe-skip-leading-whitespace nil ressolves the issue. However the docstring for evil-snipe-skip-leading-whitespace indicates that this setting should only affect behaviour for leading whitespace in a line.

Steps to reproduce

Have a line

one two three

with cursor at start of line observe:

"t " (= "t[SPC]"): cursor moved to space between one and two. It should instead go to the e in "one"
"f " (= "f[SPC]"): cursor moved to space between one and two. This is correct
"vt " (= "vt[SPC]"): "one " is selected including the space after "one". Only "one" should be selected
"vf " (= "vf[SPC]"): "one" is selected not including the space after "one". Instead "one " should be selected

Package commit

c2108d3

System Information

Emacs 29 with doom

@bschwehn bschwehn added the bug label Oct 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant