Mouse fails to set cursor position at end of line in command mode

[Manuzor]

Summary

When command_mode is active, using the mouse to change the cursor position does not work as expected in a certain case. This case is when clicking on the very last clickable position in a line, i.e. on the newline character.

It seems like the mouse click is unable to set the actual cursor position but succeeds in setting the rendered cursor position in this case.

I've already posted about this in the forums. Here's the link: https://forum.sublimetext.com/t/command-mode-cursor-jumps-back/23733

Expected behavior

When clicking beyond the last character in a line with the mouse, i.e. on the newline character, the cursor should jump and stay to the left of the newline character. Trying to insert a new character at that point should insert it before the newline character, just like when the cursor is anywhere else on that line. Also, when leaving command mode, the cursor should stay where it is.

Actual behavior

When clicking beyond the last character in a line with the mouse, i.e. clicking on the newline character, the cursor should jump to the left of the newline character. However, the cursor then jumps to the left by one textpoint. Clicking on the same spot again, the cursor appears to be in the correct position.

• Trying to insert a new character at that point puts the cursor one to the left again and inserts the character in the wrong position, i.e. before the last non-newline character in the line.
• Leaving command mode at this point, the cursor is set back one character to the left as well. Entering and leaving command mode then does not change the cursor position at all, though.

Steps to reproduce

1. Enter command mode: view.settings().set('command_mode', True)
2. Use the mouse to click on the end of some line.
3. Watch the cursor jump to the left by 1 character.
4. Click on the same spot again to see the cursor jumping to the desired position.
5. Either insert a character somehow (plugin, command) or leave command mode: view.settings().set('command_mode', False)
6. Watch the cursor jump back one character again, placing it before the last non-newline char in that line.

Environment

• Operating system and version:
  • Windows 10 Education, Version 1607, OS Build 14393.321
  • Mac OS NOT TESTED
  • Linux NOT TESTED
• Sublime Text:
  • Build 3126

[keith-hall]

When clicking beyond the last character in a line with the mouse, i.e. clicking on the newline character, the cursor should jump to the left of the newline character. However, the cursor then jumps to the left by one textpoint.

Confirmed on Windows 7 and Ubuntu 16.04. Left mouse button down = correct caret position, button up/release = move back one character. Seems like a bug in the built in drag_select command.

[Manuzor]

I have observed another detail. First you have to bring the cursor in the situation described above (click past last char once, then do it again). When you save the document now (if doesn't matter if you had changes or not), the cursor jumps back to the actual position after a short period of time.

Just thought I'd share my observation. Hope it helps.

[LandisTwo]

me too. was driving me crazy.
I disabled or removed a lot of packages, trying to figure out if it was due to a key binding.

---

It turns out that hitting 'Esc' key, when there's nothing to 'escape' from (eg, Package Panel, Console etc) enters or 'turns on' Vintage Mode (a vi emulator or 'command mode').
The way out or back to 'Visual Mode' is by,
Pressing 'i' key (that's lowercase Eye (no quotes)).
Landis.
ps, Vintage is an ignored package in Default Settings, but not in User Settings.
I thought that User settings appended Default, but apparently not.
I added Vintage to the list in User Settings and now Esc does not invoke 'command mode'.
Landis.

[FichteFoll]

Keys in the User settings always overwrite the corresponding key from the Default settings file.