When saving a newly created file, depending on the file name extension, Sublime Text sometimes adds an additional incorrect extension to the file name.
Problematic examples:
aaa.md -> aaa.md.m
aaa.cs -> aaa.cs.c
aaa.htmla -> aaa.htmla.html
The file name extension is what matters here, not the aaa part before it. Many extensions work properly. File names, such as aaa, aaa.c, aaa.css, and aaa.html are fine. There seems to be a clear pattern here relating to prefixes of the chosen extension that are known extensions by themselves.
Steps to reproduce
Start ST in safe mode
Open a new file
Save it as aaa.md
Expected behavior
The file should have gotten the name aaa.md and ST should have treated the file as Markdown.
Actual behavior
The file name has gotten name aaa.md.m and ST treats the file as Objective C instead of Markdown.
Description of the bug
When saving a newly created file, depending on the file name extension, Sublime Text sometimes adds an additional incorrect extension to the file name.
Problematic examples:
aaa.md
->aaa.md.m
aaa.cs
->aaa.cs.c
aaa.htmla
->aaa.htmla.html
The file name extension is what matters here, not the
aaa
part before it. Many extensions work properly. File names, such asaaa
,aaa.c
,aaa.css
, andaaa.html
are fine. There seems to be a clear pattern here relating to prefixes of the chosen extension that are known extensions by themselves.Steps to reproduce
aaa.md
Expected behavior
The file should have gotten the name
aaa.md
and ST should have treated the file as Markdown.Actual behavior
The file name has gotten name
aaa.md.m
and ST treats the file as Objective C instead of Markdown.Sublime Text build number
4180
Operating system & version
macOS Sequoia 15.0.1
(Linux) Desktop environment and/or window manager
No response
Additional information
No response
OpenGL context information
No response