movePrimaryCursorIntoVisibleRange is overzealous

[zpencer]

Sorry looks like my proposed fix for #2009 is causing unforeseen problems. Now the cursor is moved to the top / bottom of the screen in scenarios where it doesn't make sense. For example, jump to definition should put the cursor on the symbol, but instead we now see the cursor placed at the top/bottom edge of the screen.

[whitphx]

Thank you, but

jump to definition should put the cursor on the symbol, but instead we now see the cursor placed at the top/bottom edge of the screen.

I couldn't reproduce this issue in my env.
Could you provide sample code?