Can't get VS editor to indent case labels (set to Emacs)

  • Thread starter Thread starter _DG
  • Start date Start date
D

_DG

Re VS2005 editor in Emacs mode (options->env->keyboard mapping)

First of all, there are very few editor options for formatting C/C++
code. Only three option pages. C# has about 10, I believe.
Why are there no C++ equivalents to C#'s detailed formatting options?

In the following code block, the editor won't *accept* a tab before
the case label (much less do a correct auto-format):

switch (n) {
case 0:
break;
}

I can get around this by temporarily putting the open brace on a new
line, then inserting the tab, then re-placing the open brace. Or by
putting commenting the case label with '//', inserting the tabs, then
deleting the '//'. Tedious of course.

Also can't tab after the end of a line to add a comment. Have to lay
on the space bar.

I don't remember having those problems with beta2. Are these last
minute 'fixes'?
 
Re VS2005 editor in Emacs mode (options->env->keyboard mapping)

First of all, there are very few editor options for formatting C/C++
code. Only three option pages. C# has about 10, I believe.
Why are there no C++ equivalents to C#'s detailed formatting options?
Click to expand...

There are no C++ equivalent formatting options in VS2005. In our
judgement (and you may disagree :), it was more important to spend time
on better browsing features (for example, you'll notice that
caller/callee browsing is a C++-only feature).
In the following code block, the editor won't *accept* a tab before
the case label (much less do a correct auto-format):

switch (n) {
case 0:
break;
}

I can get around this by temporarily putting the open brace on a new
line, then inserting the tab, then re-placing the open brace. Or by
putting commenting the case label with '//', inserting the tabs, then
deleting the '//'. Tedious of course.

Also can't tab after the end of a line to add a comment. Have to lay
on the space bar.
Click to expand...

This is certainly a bug. You can log it at:
http://msdn.microsoft.com/productfeedback.
I don't remember having those problems with beta2. Are these last
minute 'fixes'?
Click to expand...

That would be very unfortunate :(

Thanks,
 
Back
Top