ember91

Results 20 comments of ember91

This can be closed due to #17

This can be closed

This may be an issue with clang-format and not the extension. To be precise an issue with the clang-format `-assume-filename` option not playing nicely with `.clang-format-ignore`. See https://github.com/microsoft/vscode-cpptools/issues/13005 and https://github.com/llvm/llvm-project/issues/113099.

I tested this with Python 3.11.5. But which rule is supposed to catch this then if not N816?

I'm a bit lost here. Eliminate what behavior of the check? That it identifies mixed case variables in comprehensions?

Any more input here? @sigmavirus24 @dhruvmanila

Yes I don't claim that the result will be much better because it supports more characters; both will with your ACP and OEM encodings support the same number of characters...

Try adding 'SetConsoleOutputCP(CP_UTF8);' at the initialization of the application. Although note that it's Windows-only, so hide it behind a define.

If you have interactive terminal input you need `SetConsoleCP` as well. But I'm guessing you don't. To me the changes look fine. With just a quick read it seems like...

I can make the changes. Three things: * I can't find `clambc.c` you mentioned but I think I have added it in the files that matter that have a `main()`...