16

This is just one of those things that I started wondering about.

Why aren't the copy/paste keyboard shortcuts (that we all love) in command prompt not aligned with the rest of the software population? I understand that it could be that historically ctrl+c and ctrl+v had different meanings in shell programs. But isn't it high time someone changed this?

Powershell was actually designed in the new century but still doesn't support ctrl+v.

Is it because windows doesn't want to break all the legacy scripts that may have assigned different uses for ctrl+v ? If that's the case, why does every major upgrade to the .Net framework deprecate some star feature from the previous version.

Everytime I do a ctrl+v on command prompt I think to my self that there must be a real good reason for things to be the way they are. I'm hoping someone would be able to tell me what it is.

Nandun
  • 333

0 Answers0