(Reported incorrectly by me before as https://bugs.kde.org/show_bug.cgi?id=347449, it's actually the C++ parser doing this). "NewGRF Meta-Language" files have extension '.nml' and mimetype 'text/plain', and have a superficially C-like syntax. '.pynml' files are similar. KDevelop 4.90.91 attempts to parse them as C++ files, and puts error highlights on almost every line. This makes them quite irritating to read. NML, parsed as C(++?): https://dev.openttdcoop.org/projects/nml/repository/raw/examples/road_vehicle/example_road_vehicle.nml PyNML, parsed as C++: https://dev.openttdcoop.org/projects/road-hog/repository/raw/src/templates/road_vehicle_properties.pynml Reproducible: Always Steps to Reproduce: 1. Open NML or PyNML file. Actual Results: File and problems view filled with errors and warnings. Expected Results: File not parsed, because it's not C or C++.
$ kmimetypefinder5 ~/Downloads/road_vehicle_properties.pynml text/x-csrc $ kmimetypefinder5 ~/Downloads/example_road_vehicle.nml text/x-csrc To fix this run `kcmshell5 filetypes`, add a NML mimetype with the patterns `*.nml` and `*.pynml` (or two mimetypes for the two patterns).
$ file --mime-type road_vehicle_properties.pynml road_vehicle_properties.pynml: text/plain $ kmimetypefinder5 road_vehicle_properties.pynml text/x-csrc This is definitely a bug IMO. The file _has_ a correct mime-type in the absence of an official NML one. Failing that, this would presumably happen for a plain-text README with a lot of C examples in it. KDevelop is producing the incorrect one from thin air (or rather flaky parsing) and then using it to do the wrong thing without prompting or an option to prevent that.
nicolas17 explained more to me on IRC about how mime-type detection works, so "The file _has_ a correct mime-type in the absence of an official NML one." is wrong. I still don't think this is sane, if the filetype detection isn't reliable it should be possible to override it within KDevelop (https://bugs.kde.org/show_bug.cgi?id=360094)?
I actually agree now that I thought more about it. Afaik in KDev4 land we only looked at the mimetype patterns. If we don't do that anymore then we may run into trouble with parsing binaries etc.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.