The project I'm working on has some files with a ".pynml" extension. These don't contain valid python code, so parsing them is pointless and leads to error underlinings and randomly highlighted areas. Doesn't seem to be a mimetype issue - 'file name.pynml' gives simply "name.pynml: ASCII text" compared to "name.py: Python script, ASCII text executable" for an actual python file. Possibly it's incorrectly matching the start of the suffix? Reproducible: Always Steps to Reproduce: 1. Have a file named *.pynml (or presumably *.py*) 2. Open it in KDevelop with kdev-python installed Actual Results: kdev-python attempts to parse file, produces nonsensical highlighting and errors Expected Results: kdev-python ignores non-python file and doesn't attempt to parse it
Remembering to check the actual mimetypes, it's text/plain vs text/x-python.
Hmm. Strange, it should only parse files with mimetype text/x-python. It also does this correctly for me: kdevplatform (language) KDevelop::BackgroundParserPrivate::createParseJob: found no languages for url KUrl("file:///tmp/test.pynml")
Odd. Files in question: https://dev.openttdcoop.org/projects/road-hog/repository/show/src/templates
I could never reproduce this, if it still exists, please reopen
Sorry, looking at the same problem now it seems to be caused by the C++ parser, so I was probably mistaken when filing this. Re-filed against the C++ parser as https://bugs.kde.org/show_bug.cgi?id=360081