DevStudio 2005 is chock-full of great new technology. One example is the "Paste" command. I bet you never thought there was anything wrong with the old way, right? Ctrl+C to copy, Ctrl+V to paste. It's simple and clear, it does the job, and it hasn't changed since around the time WordStar was released. No need.
Well, the DevStudio 2005 team thought of something: Now, when you paste a line of code which ends with a semicolon, the text editor collapses every run of whitespace on the line to a single space character, except for whitespace at the beginning of the line. No, really. That's not a joke, it's true. I'm serious! And if there's no whitespace at the beginning of the line, but there is whitespace elsewhere in the line, it indents it to the level of the previous line in the file. That happens even if the whitespace in the line was left untouched (i.e., nothing but single space characters).
Their assumption must be that in the normal case, you are adding whitespace that you don't want to add. I don't know why you'd do that, but some evil clown at Microsoft thinks he's got you figured out.
Here's the best part: If you hit Ctrl+Z immediately after pasting, the editor restores the whitespace it just removed. If you really want to undo the paste you just did (which is what Ctrl+Z used to mean, remember?), you have to hit Ctrl+Z twice -- unless it happened that nothing in the line fit the mutilation profile. In that case, the first Ctrl+Z undoes what you just did, instead of what the editor just did to screw up your code.
Oh, and by the way, if you paste in a line of text ending in a semicolon immediately preceding an existing line, it gratuitously mutilates the whitespace in the following line as well. This happens even if the pasted line's whitespace is not mutilated.
So sometimes the Undo command is Ctrl+Z, and sometimes it's Ctrl+Z + Ctrl+Z. And the paste command is now two keystrokes as well -- in most cases. But not all, and the rules for deciding what to destroy are so convoluted they take a few paragraphs to explain.
That's just brilliant: Take two of the most commonly used editor commands, and make them require two keystrokes each instead of one. But only in an arbitrary subset of cases, so you can't even just memorize the new, broken keyboard commands: You have to watch the thing every time. You have to learn to treat your text editor as a hostile entity. As if you didn't already have enough troubles already.
It also indents pasted text to the indentation level of the previous line, even if indenting is disabled. That's not just "smart" indenting being disabled, but indenting, full stop. Naturally, it indents the following line as well, just because... well... because it's more insane that way.
They don't have time to fix crashing bugs, but they have time to dream up surreal and byzantine modifications to commands whose behavior has been rigidly standardized throughout the entire industry (at least the parts that MS is aware of) for, what, 25 years? And they'll let you turn off a lot of moronic user-harassment misfeatures, but not this one. This time, there's no escape. It's the f*****g paperclip all over again.
They have utterly lost it.