This is the strangest bug I've seen, very intermittent but getting more common on my system, even after restarting VS Code and/or rebooting. I have no idea how to make a reproducible test case so hopefully someone has an idea what is going on.
When I save the C file I'm working on, the file is very strangely corrupted (probably due to the clang-format in some way). I have a short video where all I do is hit save then undo a couple times, and it shows that even the corruption is not consistent from save to save.
I just updated everything this morning but it's still happening...
VS Code Insiders build 1.17.0
C/C++ extensions version 0.13.0
Only 2 other extensions installed: Sublime Text Keymap 2.9.1 and Go 0.6.65
Entirety of my
settings.json.txt
On macOS 10.12.6 (16G29)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4