Search

Visual Studio Express 2012 Text editor not correctly handles '-' character by Gerard.S.St

Closed

1
0
Sign in
to vote
Type: Bug
ID: 778484
Opened: 2/4/2013 10:42:13 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
The following text line is not correctly handled by VS 2012:

//----------------------------------------------------------------------------------------

This line of code has 91 characters in it, but when you try to put caret to the last character, it goes to the wrong column. in this particular example it shows column number 89 instead.

This happens only when '-' character is used in source code.
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

1. Make white space characters visible (Ctrl+R, Ctrl+W)
2. Create new cpp file and insert the following line:
//--------------------------------------------------------------------------------------
3. Place caret to the end of the line

Product Language

English

Operating System

Windows 8

Operating System Language

English

Actual results

caret goes to the wrong column (number might be greater or less than number of characters in line)

Expected results

caret MUST go to the column number, which equals to the number of characters in line
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 2/25/2013 at 6:11 AM
Hello,

Thank you for logging this issue. We are able to reproduce the bug and are investigating it. We are using a different bug internally to track the work. I am marking this as a duplicate of that issue. Please stay tuned for future versions!

Thanks,
Murali
Murali Krishna Hosabettu Kamalesha | Program Manager | Visual Studio Professional - Editor team
Posted by Microsoft on 2/4/2013 at 10:22 PM
Thanks for your feedback.

We are rerouting 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/4/2013 at 10:51 AM
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)
Sign in to post a workaround.