All Forums  Visual Assist  Technical Support  BUG: .editorconfig when refactoring closed docs

You must be registered to post a reply.
Click here to register.

Screensize: 640 x 480 800 x 600 1024 x 768 1280 x 1024 UserName: Password: Format: Font Andale Mono Arial Arial Black Book Antiqua Century Gothic Comic Sans MS Courier New Georgia Impact Lucida Console Script MT Bold Stencil Tahoma Times New Roman Trebuchet MS Verdana   Size 1 2 3 4 5 6   Color Black Blue Brown Green Red Violet Yellow Message: Forum code is on. Html is off. [quote][i]Originally posted by cmartel[/i] [br][b]Environment[/b] Microsoft Visual Studio Community 2019 Version 16.6.3 VisualStudio.16.Release/16.6.3+30225.117 Visual Assist 10.9.2353.0 Visual Studio's Text Editor settings for C/C++ > Tabs is set to "Keep Tabs". The project has an .editorconfig overriding this through [font=Lucida Console]indent_style = space[/font=Lucida Console]. [b]Repro steps[/b] 1. Open the .h file (and only that) from C++ header/cpp pair. 2. Add a function declaration (or anything that'll allow a Refactor snippet) to the .h file. 3. From VAX's Quick Actions and Refactorings, choose "Create Implementation". [b]Result:[/b] The corresponding .cpp is opened and the Refactor snippet is inserted, but using tabs instead of spaces. [b]Expected result:[/b] The snippet is inserted with spaces as per the .editorconfig override. Do note that if the .cpp document is already open, refactoring will correctly use spaces instead of tabs. Likewise, if the C/C++ setting is set to spaces instead of tabs, it'll insert spaces even after automatically opening the document. I'm not sure if this is a VAX or a VS issue as I don't recall noticing this behaviour before I updated VS2019 sometime in the last month, but because it involves VAX refactoring, I figured I'd let you know. Thanks again for VAX and keep up the good work! :) [/quote]   Check to include your profile signature. Check to subscribe to this topic.