|
Don't you know WordStar?[^]
Ctrl-Insert for copy
Shift-Insert for paste
Works everywhere. Visual Studio messes it up. 
Solves that empty-line-copy problem too, from what I can tell.
* EDIT *
Oh, interesting, Ctrl-Insert and Shift-Insert are from the IBM Common User Acess (CUA)[^]
modified 14-May-15 8:56am.
|
|
|
|
|
That's the old school way of doing it. I can remember it from the DOS / Word Perfect / Quatro Pro days. Funny thing is, nobody ever considered copy/pasting an empty line back then. We did things more efficiently by using the huge [Enter] key on the keyboard.
My plan is to live forever ... so far so good
|
|
|
|
|
DJ van Wyk wrote: old school way of doing it
best way...
|
|
|
|
|
They were the ones shown on the menus in Win 3.1
|
|
|
|
|
greldak wrote: They were the ones shown on the menus in Win 3.1
You're right. That's how I learned them and I've never forgotten them. They work in places the other hotkeys don't.
|
|
|
|
|
Even more bizarre is that someone had the foresight to make that behavior configurable.
Marc
|
|
|
|
|
I'm gonna guess that in the early days copy just copied whatever was there even if it was nothing, people kept complaining, eventually they added in the option to make it behave more sensibly but didn't want to make the default different to accustomed behaviour.
Which is a sensible general policy.
True sense comes, however, from not blindly applying your policy, no matter how sensible it may be.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
|
|
|
|
|
IIRC, copy only ever did anything at all if there was a selection - and most apps work that way even today.
The whole idea of copy working on non-selected data is bad, I think - but I wish it worked in MS error message boxes where you can't select anything anyway! 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Ctrl+C works in "most" error message boxes. It copies the complete contents + title + buttons as text. I love it. You don't need to "select" anything except to have the message box focused.
Sample:
---------------------------
Microsoft Visual Studio
---------------------------
Cannot move 'RandomFile.Debug.config'. The destination folder is the same as the source folder.
---------------------------
OK
---------------------------
|
|
|
|
|
You have hit the nail on the head.
This is the reason why copying non-selected makes you shoot blanks, but it lets you copy the un-selectable.
Sort of nice.
I am a bit pissed off about this as I didn't know about this until your post.
So Thanks Corneliu.
There is always a reason.
"Rock journalism is people who can't write interviewing people who can't talk for people who can't read." Frank Zappa 1980
|
|
|
|
|
Using copy on a line with nothing selected actually copies the whole line including CRLF; pasting that puts the whole line you just blank-copied above the line where your cursor is sitting. SSMS, VS and Sublime all do it and it's pretty nice once you get the hang of it.
Feel your pain on the MS error boxes though 
|
|
|
|
|
What's bizarre is why y'all are making such a deal of it. It's a FEATURE. You put your cursor on any line (w/out selecting anything) and Ctrl-C copies the whole line. That's useful. No mouse necessary.
You DO know that VS has unlimited memory on the clipboard, right? If you accidentally copy something when you meant to paste, just Ctrl-Shift-V a couple times and VS will cycle back through your recent clipboard items. Easy workaround to your stated problem.
Chill. No smoking necessary.
|
|
|
|
|
kdmote wrote: just Ctrl-Shift-V a couple times and VS will cycle back through your recent clipboard items.
Huh, no I didn't know that!
Caveman Marc
|
|
|
|
|
Interesting way to clear the clipboard so as to not have 'forgotten' items in there that may be inadvertently posted later.
|
|
|
|
|
Tim Carmichael wrote: way to clear the clipboard so
I've done that when I've copied and pasted large amounts of information from other projects or applications just to clear the clipboard.
It was broke, so I fixed it.
|
|
|
|
|
What ever happened to the multi-chased copy paste?
Mongo: Mongo only pawn... in game of life.
|
|
|
|
|
It was too multi-chaste, and died out since it didn't copy...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Hold still. Bubba the angry male sheep wants to hurt you now.
Software Zen: delete this;
|
|
|
|
|
I wish they would separate that option to one for copy and one for cut. Because I agree that copying a blank line is just silly. Cutting however?
When I'm rearranging code (commenting / moving similar methods/props next to each other, etc..., ergo, a lot of cutting/pasting), I use ctrl-x to cut (read: delete) blank lines all the time. Much easier to do with one hand on the mouse, and the other on ctrl-x. ctrl-delete requires me to leave the mouse or contort.
|
|
|
|
|
And I was just about to enable that option... good catch.
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
Why won't you just press delete ?
|
|
|
|
|
Because some(many) times the "blank" lines have extra spaces or tabs in them. Delete will only get rid of one of the characters. ctrl-x eliminates the whole line. And I think these faux-blank lines still count as blank as far as this option is concerned.
Also: since this is usually in the midst of moving code, my hand is already over the ctrl-x keys.
|
|
|
|
|
In VS I prefer to use [Ctrl]+[Shift]+[L] to remove empty lines. That way I don't lose what's in the clipboard. It normally happens when I decide to move chunks of code around by cutting what I want to keep, removing all lines to clean up, then going to the new location and pasting. That way I don't have to scroll around or remember where to clean up again.
My plan is to live forever ... so far so good
|
|
|
|
|
If you think about the vast number of options in VS (in Tools => options), and wonder why and WTF a lot of them do, then ya, it makes you think "Why MS, why?"
But what really bugs the piss outta me is when menu & shortcut options change from one version of VS to another.
If it's not broken, fix it until it is
|
|
|
|
|
That is the second setting I change when installing a new copy of any version of VS.
My plan is to live forever ... so far so good
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
