Could these Cursor problems be Setting or Theme issues? Or is it just my Mac's G.E. BroadCom chip and another 2018 “machine lag” issue? Don't dismiss that, for anyone with a professional Apple device, but lets move on...
Selections and Search do things to the cursor that are not consistent, and are not expected. Now, this is posted as a technical support request, and sorry if this uncovers unexpected for Sublime Support, because it could mean lots of fix-ups. Or, it could be Sublime like Microsoft makes lots of arrangements with BIG corporations, a use it or lose it agenda thing (DOD vs. $an Bernardino, and lots of even more messy document format directions).
In this image, all lines are selected after edits described and dicussed below the image.
Alt-drag action: line 21 auto line wrap, line 22 forced line wrap (settings wrap)
1. Why a cursor at right end of line 21?
2. If line break cursor expected on end line 21, why not end line 22?
3. Far better to provide two different cursor colors, existing cursor and color and add additional cursor of another color or color/width to show forced or manual line breaks.
Change window width and life could seem really weird!
This is a truly excellent half-_ssed proofing feature, though it may not be for all users.
1. Is this window width effect intended, or even scalpable in Settings?
2. Can this effect be adjusted at all, in Settings?
3. Would anyone dare to recoup an old article, or create a new one defining publishing line breaks, and how Sublime can show where control might be needed (window width fall-out, inconsequential, or wondereful benefit)?
4. Question for advanced users, if we are coding text column widths for mutiple columns, is there a way to highlight-focus the code of the column under the cursor? Or is that a new feature request for developers of the Sublime Core?
5. This is a request (from outside industry) to complete this proofing feature. Provide app state capture where such line wrap cursor controls and highlight can be trapped and shared then further edited across Sublime instantiations and sessions. ...enough on cursor appearance.
Cursor behavior is another concern.
Cursor in <key> tag do search for key.
Whoah! The opening key. Not that closing key!
1. Does this serve any purpose?
2. If it is purposed (e.g., as a way to find closing tag) perhaps Subime could introduce coding industry to dual shade key highlights - one shade for opening tag, another shade for closing tag (present underlining method is very difficult to detect visually)?
Supposition and wishful thinking maybe, but if the app differentiates opening and closing tags this way, is there a keyboard shortcut toggle, to bounce display focus back-and-forth between opening and closing tags? Yes please?
If we close our eyes and walk into a wall... we have still just walked into a wall. -- Bhudda