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

when cursor at the end of a python line, should have better algorithm to decide how to jump #63

Open
redguardtoo opened this issue Sep 24, 2015 · 2 comments

Comments

@redguardtoo
Copy link
Owner

to jump or not jump
or let user decide how to jump

@quicknir
Copy link

Helping a user in the spacemacs gitter, they were having some issues with this. I agree with them that in some places the algorithm is a bit poor; based on what I've seen I think the algorithm is overall arguably worse than just using "simple" (at least it's more predictable). Example:

def foo():
    bar1()
    bar2()

With the cursor on the closing paren of bar2 call, it jumps back up to the d in def. I can live with that, I can see the argument for it. But it also jumps there when the cursor is on the closing paren in the bar2 call. I think this is pretty hard to justify.

At the bare minimum, when you're on a line that's not the end of a python indentation level, evil matchit should have the same behavior as the simpler behavior you usually see in C style languages. Jump to matching delimiter (the usual suspects), or do nothing if not on one.

@redguardtoo
Copy link
Owner Author

redguardtoo commented May 12, 2018

8a10046 fix python issue (Chen Bin)

redguardtoo pushed a commit that referenced this issue May 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants