Hello @loic-lopez!
The reason why your *.m files got processed by SonarLint is that we detect languages based on file extensions, and .m extension is standard for Objective-C language. So this files are possible candidates for analysis.
But Objective-C language is disabled for SonarLint by default. So real analysis and displaying issues should be skipped in your case. Could you please elaborate more what is bothering you in SonarLint behaviour? Do you see any issues for this .m file?
I’d ask you post to this topic your SonarLint logs. You can see here how to get them. It will help to clarify what is happening.
Also will be great if you provide content of your sample .m file to reproduce the issue and the screenshot with unwanted SonarLint issues or messages you getting during your work with Matlab files.
Have a good day!