However, since what this typically means in practice is you'd either cut until the next period, or until the end of the line, in the absence of an "end of sentence" keybinding, my approach to this would simply be to either cut until the next period, or until the end of the line as required, which I believe is a wholly reasonable alternative.
The former would be:
{mark} {search} . {enter} {cut} {endoffile} {paste} (7 keystrokes)
The latter would be {cuttoend} {endoffile} {paste} (3 keystrokes)
The 7 keystrokes become very vim-competitive when you realise that d)Gp actually fucks up in the typical scenario, since usually what you want is NOT to paste after the first character of the last line, but actually in a new line below the last one. Which means you don't actually just do `p`, but something like `o ESC p` instead.– sometimes needs to make a few quick edits right from the terminal (but prefers a proper GUI text editor like VS Code for longer sessions)
– is accustomed to the keyboard shortcut conventions of desktop applications on Linux/Windows[1]
– occasionally, wants to use the mouse and expects it to work in the terminal like it would in a proper GUI text editor.
Micro fulfills all these needs with its default configuration. It is one of the first things I install on a Linux box, be it a desktop or a server.
[1]: https://en.wikipedia.org/wiki/Table_of_keyboard_shortcuts
I feel this kind of editor is for the sophisticated minimalist, used alongside a 60% fancy keyboard with ceramic key caps.
I see comments about this being good for "beginners", and I wonder what definition they are using. Make them use a basic graphical editor like gedit.