Thanks Jon. Any chance you could take a look at the line wrapping behaviour with punctuation and caret movement, they’re a real PITA for editing plaintext (prose) in Sublime and hopefully are a fairly trivial fix. Obviously this applies particularly when editing text/prose (ie. plaintext) and arguably some of this makes less sense in a programming context. Perhaps the new wrapping rules could be applied through a config setting per-User or per-Filetype, so that users could configure this behaviour for their own filetypes.
Examples.
- Cursor left or Ctrl+cursor left from the second character of a wrapped line moves the caret to the previous line, whereas Home correctly moves the caret to the beginning of the word at the beginning of the line.
- Words beginning with a full stop, minus or comma (plus a few others I guess) will be wrapped leaving the first character hanging at the end of the previous line
- Words with other punctuation characters like brackets, square brackets and curly braces leave the leading punctuation char hanging at the previous line end, even if there’s no space after it. So we see wrapping behaviour as below:
sometext (
see below)
Should be:
sometext
(see below)
And without the space after “sometext”:
sometext(
see below)
Should be:
<wrap entirely>
sometext(see below)
TIA
ps. Like the new block caret. Can we optionally have this one outside Vintage too? Thought I’d ask first