dear zed ppl, PLEASE PLEASE PLEASE configure your language detection properly wrt C and C++! every single editor on earth makes this exact same mistake where they think all C is valid C++ (it's not, at all), and mistakenly recognises C files as C++, even when there's an accompanying compile_commands.json file that specifies a C standard and even when files contain invalid C++ (but valid C)
it's a delightful little editor if it weren't for this thing...
haiku2077
You can customize the rules for detecting a language by file name/path in your settings. The problem is in cases like creating a new file the editor has to guess.
it's a delightful little editor if it weren't for this thing...