This patch addresses 3 issues
- Currently if you try to convert the cursor to coordinates and then convert these coordinates back to a cursor again, it produces an invalid cursor (-1, -1) when the original cursor is located at the end of line
- Converting back to cursor coordinates that have been produced by cursorToCoordinate(view->cursorPosition()) and cursorPositionCoordinates() doesn't always produce the same results as the includeBorder option doesn't seem to be used consistently.
- Although I cannot find a test case for this, it doen't seem to make any sense the line scrollPos(max, max.column(), calledExternally); in KateViewInternal::makeVisible function. Was it supposed to be that way (ie force when the last line is not empty and not force when it is), or is it just a typo? :\ I would appreciate any reasoning about this!