The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
Recently I installed Linux and had to use vi to edit some files. I hadn't used the godforsaken thing in about 30 years but managed to do what was needed without hopelessly corrupting those files. I now believe in muscle memory, since it is the only explanation for how I could insert, replace, cut, and paste text and quit with or without committing the changes.
In a Lounge post a couple of weeks ago, I asked about using Windows 10 to develop C++ for Linux. VS Code seemed to be a clear winner, so I'll likely switch to it someday. What's blocking me is builds, for which I use VS2017.
For WSL, MS recommends CMake. That looks to be about as fun as vi, so you'd think MS would provide a tool for converting VS project files to CMake. Think again.
But I did find a tool[^] that supposedly does it. What it generated seemed to do most of what was needed, but it failed on a shared properties file that controls various compiler and linker settings. So I'm stuck with VS2017 until this tool gets fixed or MS gets their act together. Porting to Linux isn't urgent, so I'd rather wait than struggle with CMake.
A) Try parsing the syntax. Significant whitespace presents real technical challenges to parsers.
B) Try remembering the syntax. If it can't be easily remembered, it's always going to be niche**. See also, vi.