Ctrl+Backspace deletes too much text - by XtraPants

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 533093 Comments
Status Closed Workarounds
Type Bug Repros 5
Opened 2/11/2010 10:03:42 PM
Access Restriction Public


if (pszValue)
    | <-- Cursor

When I press Ctrl+Backspace with example above, it deletes the open brace on the preceding line.  This was NOT the case in VS08.

The same bug occurs with statements like this:

void main()
    int i = 0;
    | <-- cursor here


pressing Ctrl+Backspace deletes the semi-colon on the line above, instead of the VS08 behavior of deleting whitespace and keeping the cursor on the same line.
Sign in to post a comment.
Posted by Microsoft on 4/16/2010 at 2:22 PM
Hi XtraPants,

I'm writing to let you know that although we couldn't fit this in before VS 2010 RTM, we just recently checked in a fix for this Ctrl+Backspace behavior for the next version of Visual Studio. We will also consider the fix for VS 2010 SP1.

Thanks again for your feedback! Even though we can't fix everything for a given release, we really do revisit Won't Fix-ed and Postponed bugs. As in this case, your feedback can make a difference even months later, so thank you!

- Brittany
Posted by Microsoft on 2/15/2010 at 10:53 PM
Hi XtraPants,

Thank you for reporting this issue. We agree that this is a behavior difference from VS 2008 and a slight annoyance. The behavior difference is caused by the fact that VS 2008 inserted actual whitespace on blank lines, whereas VS 2010 treats that space as "virtual" whitespace until a character is inserted. The word navigation logic (e.g. in delete previous word) interprets real and virtual whitespace differently, so VS 2010 deletes the word *before* the whitespace instead of deleting the whitespace itself as in VS 2008.

We unfortunately don't have time to update this logic in the short time between the VS 2010 RC and RTM, so I'm resolving this bug as Won't Fix for this release. However, we do agree that the VS 2008 behavior is preferred, so this bug will remain in our database to be revisited for a future verion of Visual Studio.

Thanks for trying Visual Studio 2010 and sending your feedback!

Brittany Behrens
Program Manager, VS Platform
Posted by Microsoft on 2/14/2010 at 12:15 AM
Thank you for reporting the issue.
We were able to reproduce the issue you are seeing. We are routing this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 2/12/2010 at 7:02 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)