-1
Fixed

Ctrl-K doesn't quite do what emacs users would expect

David Alexander 7 years ago • updated by Jon Skinner 7 years ago 1
Ctrl-K, in emacs (or, on OS X, in the many applications, such as TextEdit, that have emacs-compatible bindings), kills the current line from the cursor to the end of line; invoking Ctrl-K again, the cursor remains fixed but the EOL is killed, bringing the text of the next line up in front of the cursor.

SublimeText handles the first Ctrl-K correctly*, but subsequent Ctrl-K's cause ST to delete a letter backwards---which I find bizarre.

* Not quite correctly: it doesn't place the killed line in a kill buffer. Even lowly TextEdit seems to do this: try Ctrl-K, then Ctrl-Y

I laud your efforts to make SublimeText more friendly to Emacs refugees.

Answer

Answer
Fixed
This is fixed in dev build 2024 (http://www.sublimetext.com/dev or http://www.sublimetext.com/forum/viewtopic.php?f=2&t=1656).

There's also now a kill ring and marks in this build.
Answer
Fixed
This is fixed in dev build 2024 (http://www.sublimetext.com/dev or http://www.sublimetext.com/forum/viewtopic.php?f=2&t=1656).

There's also now a kill ring and marks in this build.