You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
to jump or not jump
or let user decide how to jump
The text was updated successfully, but these errors were encountered: