Hi,
I am not sure how to define this issue. Some time ago I tried out CodeMap plugin. Since then, I have deleted it as well as the Package Manager itself.
However, sometimes the formatting of seemingly random markdown documents switches to “CodeMapMarkdown” or just “md”. This causes an error of unsupported formatting to pop up.
How could I completely get rid of the undesired specific formatting?
Maybe there’s a syntax specific settings file left behind in your User package, which assignes *.md extension to the no longer existing syntaxes?
In ~/.config/sublime-text/Packages/User/, there’s Package Control.sublime-settings (yes, the file name has a space) with only these lines (like I said, Package Control has been uninstalled):
{
"bootstrapped": true,
"in_process_packages":
[
],
"installed_packages":
[
],
}
There’s also a whole CodeMap folder with several sub-folders and files.
Should I delete all that?
Preferences > Browse Packages opens the Packages folder; any folder that exists inside of that location is considered to be a package, and any resource files that appear inside of such a folder will apply.
Similarly, from that folder if you go up one folder to the parent, you will see a sibling Installed Packages folder; any sublime-package file that exists in that folder is a package and will be loaded.
That said, if you previously told Sublime to open all files with a specific extension as some other type of file, then it will remember that even if you removed the package; so you need to check your User package for a sublime-settings file that looks like it’s named the one that is causing you problems, and if you find it try moving it away to your Desktop or similar, then close and re-open the markdown file and see if the problem is gone.
Such file may also appear in the package you mentioned, if it did something janky like force a syntax on you just by having it installed (which is considered Bad Form ™).
Thank you for the comments, @OdatNurd
I have removed everything that had “CodeMap” and “PackageControl” in its name. ST has launched and seems to work fine so far.
It’s strange that removing the extension and Package Control left the setting in place.
Generally speaking, user defined settings and preferences are left behind when things are uninstalled (not just in Sublime, but just in all software in general) so that temporary removals of things for testing or while performing an upgrade don’t cause you to lose work or progress.