pgScorpio

And again the code style check failed, while I have ran `make clang_format` and again the result of the auto-build clang-format is NOT according the code style! I'm really considering...

@ann0see > Did you see the error? Cross platform development is probably really hard. Now I do see it! Thanks!. Somehow missed that one in the search and replace :=((,...

@hoffie I completely understand your confusion, but that's because I terribly messed up some things by opening a PR from my master (Sorry!!). This causing PR's, my master updates and...

As mentioned in the other topic: See [here](https://docs.github.com/en/get-started/getting-started-with-git/configuring-git-to-handle-line-endings#per-repository-settings) or [here](https://stackoverflow.com/questions/9976986/force-lf-eol-in-git-repo-and-working-copy).

OK, (I thought it should already be clear from the mentioned related topics.) As, by default, line endings are converted to the OS standard clang-format will sometimes have different results...

We also might want to add these folders to .gitignore ?

OK I've done some investigation, and I discovered a lot... I searched on several forums, encountering a lot of the same or similar problems, but no solutions that work on...

> I'd suggest not to discuss that in this PR but in a issue of the type I mentioned: open a PROJECT: Sound-Redesign issue with a checklist, what you plan...

> How should we proceed here? Can you live with the current behaviour? Yes I can, since there is a work-around: Do not build from the root folder but from...

> Did you do a git rebase? I think there's something wrong with this PR (since the commits from master show up). Yes I just did a rebase, but not...