New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File type detection conflict between matlab and octave. #20

jarekwg opened this Issue Apr 19, 2016 · 3 comments


None yet
2 participants
Copy link

jarekwg commented Apr 19, 2016

Both use .m files, so Atom has no way of knowing which language to use.

Would be nice to see an option to disable one of the languages entirely so that it doesn't mess with the other. At the very least, I'd like to disassociate the .m extension from octave.

I downloaded this package to use purely with matlab code, but currently I'm getting every file showing up as octave.


This comment has been minimized.

Copy link

abbiekressner commented Jun 3, 2016

I have the exact same problem. Have you come up with a solution, @jarekwg?


This comment has been minimized.

Copy link

jarekwg commented Jun 4, 2016


Didn't find a proper solution, however:

i) if you manually set the language to MATLAB in the bottom right, atom will remember your choice for that file (at least in the short term). This solution becomes tedious very quickly if you have a lot of .m files though.

ii) you can apply all formatting preferences (tab width, etc) in the octave section of this extension's settings, then just let atom autodetect your files as octave.

Neither option is great, but I ended up going with second as I had quite a number of files to work with.


This comment has been minimized.

Copy link

abbiekressner commented Jun 6, 2016

I think I actually found a working solution. I installed Atom's file-types package. Then I put the following lines in my config.cson.

  m: "source.matlab"

After restarting Atom, Matlab files are automatically recognized as Matlab instead of Octave. Hope it works for you too!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment