Open wrgallo opened 3 years ago
I've filed a VS feature request at https://developercommunity.visualstudio.com/t/C-code-folding-for-region/1418674 since some of the outlining is implemented in our shared code.
It would be good if someone could get #pragma region
recognition added to gcc as well.
Is there any plans to add //#regino folding in upcoming update? Can you provide any settings configuration to make //#region folding to work for now?
Is there any plans to add //#regino folding in upcoming update? Can you provide any settings configuration to make //#region folding to work for now?
I would like to know that too...
At this moment I am using custom region folding with this extension, and this piece of JSON:
"maptz.regionfolder": {
"[cpp]": {
"foldEnd": "//#endregion",
"foldEndRegex": "[#]?endregion",
"foldStart": "[NAME]",
"foldStartRegex": "//[\\s]*[#]?region[\\s]*(.*)",
"disableFolding": false
}
}
It works with:
//region
... //endregion
//#region
... //#endregion
// #region
... // #endregion
But unfortunately, everyone that opens the code, needs that extension installed and configured the same way so the folding regions actually work.This issue (and/or the linked VS one) could use more upvotes. It's not currently planned for a update in the near future.
Is it thar hard to implement this feature? Maybe you can take code from #region folding for VS Code extention and it wil be done? 🤭
@Aukstkalnis I don't know if it's hard or not. We're just working on other features at the moment.
A quick grep of the source code with pragma
or region
didn't return anything likely to be where this is defined.
Can anyone who knows the project structure point me towards where/what to look for?
@SubaruArai The code folding code is implemented in our closed source cpptools process that is shared with VS.
@sean-mcmanus Oh, okay. Thought I'd make a PR if it was open source. Thanks anyways!
+1
after I write #endregion it's not clear how to write text under the fold
Type: Feature Request
Please make
//#region
and//#endregion
folding available on VSCode for C/C++ too.Feature request suggested by @Colengms in https://github.com/microsoft/vscode/issues/123016#issuecomment-837074185_
The documentation describes that C/C++ region should be defined with
#pragma region
and#pragma endregion
, although many C/C++ application complain about unknown pragma, generating many warnings. In the very same documentation, the default for many languages is//#region
and//#endregion
which is definitely the very best choice for C/C++. There are VS Code extensions like this that try to fix these annoying issue, but they create other problems, since single line comments should never use/* */
, it makes harder to comment out a block with regions inside.#pragma region
almost always require to disable unknown pragmas with the compiler flag-Wno-unknown-pragmas
, which may hide useful warnings such as the typo#pragma ocne
.#pragma region
.#pragma region
such as this. Which would never happen if//#region
would be a default.#ifndef MY_REGION_NAME
...#endif
, which may lead to pieces of code being ignored by the compiler if the region is a duplicate name.#region
inside line comment), but VSCode fails to fold, since#pragma region
should have been used instead.VS Code version: Code 1.55.2 (3c4e3df, 2021-04-13T09:35:57.887Z) OS version: Windows_NT x64 6.1.7601 ms-vscode.cpptools Version 1.3.1: April 19, 2021