cursor location seems wonky after coercion

[ivar]

This might be too subtle/minor to bother with, but after I use one of the coercion functions in abolish.vim, the next time I use the 'j' key to go down a line the cursor appears in an odd location on the subsequent line. I can mitigate this by navigating along the current line (ie: with 'l' or 'h') before descending but it's a bit of a pain.

[tpope]

Whoa, weird. Looks like it might be an issue with setpos(). Not sure off the top of my head a good way to work around it.

[qstrahl]

Just chiming in to say I noticed this behavior too On Dec 23, 2013 6:07 PM, "Ivar Vasara" [email protected] wrote:

This might be too subtle/minor to bother with, but after I use one of the coercion functions in abolish.vim, the next time I use the 'j' key to go down a line the cursor appears in an odd location on the subsequent line. I can mitigate this by navigating along the current line (ie: with 'l' or 'h') before descending but it's a bit of a pain.

— Reply to this email directly or view it on GitHubhttps://github.com/tpope/vim-abolish/issues/21 .

[ri-aje]

me too. in my case, a j always brings me to next { in the next line. this degrades my efficiency when quickly applying the same coercion over multiple similar objects with j+dot. macro helps, but sometimes it doesn't worth the hassle to make one. any chance to fix this?

[tpope]

I feel like it's a Vim bug. It's probably possible to work around if someone wants to investigate.