雪竜 (Tommy Li)

> Try to get logs from ~/Library/Logs/DiagnosticReports I wanted to, but when the crash happens nothing appears in that directory.

I have opened a PR #1933 as a temporary fix to resolve crashes on launch seen on Catalina. CC @hayatae

It does seem that there is a considerable amount of legacy Apple API usage (especially OpenGL oof). Apple is not known to be generous on backwards compatibility, maybe it's time...

Also, first seen in Catalina, user must grant StepMania "Input Monitoring" privilege in System Preferences > Security & Privacy, otherwise keyboard input would not work.

Since the macOS support is already being actively worked on, I'll close my PR.

Hi @sailro, I saw that the support for suppressor was added in a while ago (https://github.com/OmniSharp/omnisharp-roslyn/pull/2182). From my testing, at least USP0001 and USP0003 is working. I updated the screenshot...

I managed to get debugging working by building a debug version of the analyzer DLL and attach a mono debugger to OmniSharp. From my observation, breakpoints placed at the start...

> Could it be related to a custom `.editorconfig` file entry somewhere? Or perhaps given the severity level (like `suggestion`), Omnisharp is enabling/showing the `CS8618` analyzer but not passing suppressed...

I'd say this repo does not have a lot going on and is easily maintainable by oneself. I have my own fork of this repo and so far I have...

@Colengms Thank you for the explanation. I understand the behavior now. My question is: for each supported IntelliSense mode, does C++ Extension do something special for each mode? My expectation...