![]() In C# files the intending can be really inconsistent, i've seen it happen a lot, but right now, can't get a good repro, but guarantee i've seen it happen a lot, i'm wondering fiddling with some of the setting investigating I got it working right for a little while in C#. I'm thinking what might be happening, and makes the most sense to me, most everyone leaves all the "Auto Formatting" on and they have "On Enter" reformat, just find it too distracting. First thing i'll do is go in to Tool::Options then Languages and set "Indenting to" "BLOCK". Normally i turn off all auto formatting and will normally fix up the code as desired. I'm working in a few languages and file types. ![]() Hope i didn't add confusion, Adding the comment i left on the "Developer Community". The team will review the feedback and notify you about the next steps. We have directed your feedback to the appropriate engineering team for further evaluation. Original Comments Visual Studio Feedback System on, 03:16 AM: Not sure when started, bouncing between VS 20, never have seen the problem in 2017, can’t say it ever worked in 2019 for that matter. Appears “INDENTING is behaving as “NONE” is selected. When you select the editor’s setting for “Indenting” which can be one of, selecting ‘BLOCK’ the cursor, most of the time, upon present ENTER goes to column 1 on the next line. ![]() But it is happening again… The title info for the original report is:ĭATE: Olaf van der Spek reported, 12:54:20 PM Ported from dotnet/roslyn#44607 by issue has been moved from a ticket on Developer Community.įound this problem was reported before, appears to have been reported as fixed. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |