this only selects the current word.

Ok, it only selects, agree your op said that, but I misunderstood due to the strength of the preconception that ctrl-c copies. Shows what the power of that expectation is.

Agree with @ntrel that there are other adjacent keybindings with risks, but ctrl-c/v is likely the most common.

Agree with @b4n that the suggested behaviour is confusing.

A quick survey of what the editors/IDEs I have here (Linux) do on ctrl-c without any selection:

Vscode: copies line ... eeek!!! bet this is where the idea for all the requests comes from
Eclipse: does nothing
Gedit: does nothing
Xed: does nothing
Scite: does nothing
this github window: does nothing
emacs: does nothing, well actually without selection its a command prefix, but its copy with a selection, ahhh emacs ;-P

Adding unusual behaviour to common actions is a user trap, even if its safe behaviour (just select) its likely to be confusing. And selecting it looks like the word was copied, but its not.

Whilst the select word keybinding is awkward (its three key left hand only), if you use it enough for it to be a significant hindrance to your workflow you can re-define it to another binding in preferences. And of course select word is double click too.

Better not tinker with the behaviour of one of the most common user actions.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.