2 differences with other vim editors

[r3sist-uniq]

1. If you select a piece of text with visual mode (for example manually with j,k) and go into normal mode - it deselects the text which was selected visually AND also puts the cursor to the new location (depending on whether you went up with j, or down with k) kV doesn't do this i think.

2. when I am in insert mode and i press ^C to go into normal mode if i am at the first character of the line, it goes back up a line (to the last character of the line above) not sure if that's supposed to happen

[godbout]

so. kV needs Accessibility data to do proper text calculations. if an app doesn't implement the macOS Accessibility (or not properly), kV needs to revert to basic key mappings to try to achieve Vim motions. this is what the "Strategies" are about, which you can find about in the Docs (docs.kindavim.app) and in the kV itself, in the Settings, the Families Pane.

when kV is or has to use the Keyboard Strategy because there's no proper AX data, it can't know where is the end or the start of a sentence, etc., etc. so yes, in that case, the two cases you're mentioning happen. the reason is because there's no way for kV to know, so it can only be approximative.

if the third party app respects the macOS Accessibility, then kV follows Vim in the two cases you're mentioning. see the screencasts attached. first one show it doesn't go to the previous line. second shows the carets goes to the head of the selection (in Vim when you select, there's a head and an anchor. the head is the part that moves. kV respects Vim's behavior by always going back to the head.)

so basically, no bug. what you're seeing is because you're using an app that doesn't have proper AX data, so kV has to use key remapping, and therefore cannot calculate precisely like it would do if it had access to the necessary data.

1.mov

2.mov