Packages/Markdown/Markdown.tmLanguage file doesn't belong to this plugin. The reason may be this:

1. Before installing the plugin, you had a markdown tab open which used the mentioned syntax file.
2. You installed the plugin and the plugin disabled the native markdown package (this is intentional)
3. You hot exit ST
4. You restarted ST and for the already existing markdown file, "hot exit" feature tried to use the disabled syntax file
5. That syntax file isn't available to use any more and you got that error

Thanks for the response! 1. was the issue. Might want to mention that users should close all markdown files in the installation instructions.

Also might want to be more explicit that users will have to edit the User Markdown.sublime-settings, not their User Preferences.sublime-settings, to modify defaults you've set. I was perplexed after changing my User Preferences color_scheme to MarkdownEditor-Dark, that it only took effect for non-markdown files. Figured out I needed to change the setting in User/Markdown.sublime-settings (Preferences -> Package Settings -> Markdown Editing -> Markdown GFM Settings - User).

I'd personally much prefer MarkdownEditing didn't force font face, font options, line padding, caret style, etc. on users as I had to go overwrite all of that with duplicate lines from my User Preferences file. Perhaps leave such items commented out for users to try.

My list was stages of a single scenario, not different scenarios :)

Might want to mention that users should close all markdown files in the installation instructions.

Documenting this won't help I think, because nobody will read 10 pages fully, before installing a plugin. As a second solution, after installation, programmatically cycling through open markdown tabs and enabling the new syntax on them doesn't seem a good idea to me, too. Trying to be too clever is usually a bad thing for software.

Also might want to be more explicit that users will have to edit the User Markdown.sublime-settings, not their User Preferences.sublime-settings, to modify defaults you've set.

You are the best person to do that edit. PR welcome.

I'd personally much prefer MarkdownEditing didn't force font face, font options, line padding, caret style, etc. on users as I had to go overwrite all of that with duplicate lines from my User Preferences file. Perhaps leave such items commented out for users to try.

Wide blue caret is an important aspect of this package. For the rest you look right. @ttscoff Sorry to disturb you Brett but what do you think about this? Too many users have complaint for these settings. Shall I comment out those?:

"font_face": "Menlo",
"font_options": [ "subpixel_antialias", "no_round", "directwrite"],
"line_padding_top": 2
"line_padding_bottom": 2,

The font and padding options were my own preferences, back when this
package was still opinionated. I think that laying down some generally
acceptable defaults is still ideal, though. It's easy enough to modify
them, not sure why we shouldn't have some sort of groundwork laid out.

Overriding font settings is not a good solution for users because in that case they have to maintain two files for the same settings (ST user settings and markdown user settings). Unsetting instead of overriding is on the other hand not possible (they have to install the package via git and create a personal branch to achieve this). It seems these reasons require us remove font settings from the default files (also line height settings).

Fine by me.

On 4 Dec 2013, at 19:46, Ali Ayas wrote:

Overriding font settings is not a good solution for users because in
that case they have to maintain two files for the same settings (ST
user settings and markdown user settings). Unsetting instead of
overriding is on the other hand not possible (they have to install the
package via git and create a personal branch to achieve this). It
seems these reasons require us remove font settings from the default
files (also line height settings).

---

Reply to this email directly or view it on GitHub:
#115 (comment)

Not related but I gave a bluish color to links in the latest version. I'm the last guy on earth to be designer, please don't hesitate to edit the color if you want. The only thing I wanted to achieve was highlighting them slightly differently from the rest of the text.

@davidmarble I've removed the font declaration. It will be available in the next update (which may take days/weeks). The commit and the PR

Also might want to be more explicit that users will have to edit the User Markdown.sublime-settings, not their User Preferences.sublime-settings, to modify defaults you've set.

I've improved README for that. The commit

Fwiw, I have Sublime Text set to reopen all previously open documents/projects on launch. Closing all open windows then restarting Sublime Text stopped the error displaying on ST launch for me.

Thx @oli, I was also getting this warning after installing MarkdownEditing plugin. Closing all MD open files and restarting Sublime solved the warning for me too.

On a separate issue:

You installed the plugin and the plugin disabled the native markdown package (this is intentional)

For those who, like me, after uninstalling MarkdownEditing plugin, are not seeing the default Markdown syntax highlighting as an option anymore, you just have to manually re-enable the Markdown package again: cmd+shift+p, then select "Package Control: Enable Package", then select "Markdown", or through the User's Preferences.sublime-settings file.

After I remove this Plugin from my Sublime 3, the original Markdown highlighting got removed as well. I have no Markdown highlighting any more.

ST doesn't highlight markdown out of the box.

On June 19, 2014 7:31:48 PM EEST, Greg Wang notifications@github.com wrote:

After I remove this Plugin from my Sublime 3, the original Markdown
highlighting got removed as well. I have no Markdown highlighting any
more.

---

Reply to this email directly or view it on GitHub:
#115 (comment)

I may have installed that syntax definition myself from years ago, but it still means the plug-in has overwritten my existing definition files without backup, and delete all the definition after remove.

Or maybe this should be a Package Control problem...

Nope, it is just automatically disabled. You have to enable it manualy. See here

Note: Sublime text has a native tiny package for Markdown. However, when MarkdownEditing is enabled, native package causes some conflicts. For this reason, MarkdownEditing will automatically disable it. Since it doesn't bring anything new over MarkdownEditing, this is not a loss. But remember, when you disable MarkdownEditing, you have to reenable the native one manually (if you want).

Cool. I didn't noticed that. Thank you.

@albertboada Thx!

@oli Thank you! Closing all open files and restarting ST3 fixed the issue for me too!

Just to add a note for those that may still have the issue even after restarting ST3. You may have to re-enable Markdown for the offending tabs to appear so that you may close them.

I had this box appear on Windows. Only way I could get that message to not appear, and this plugin to work, was to re-enable the default Markdown plugin. Now it seems to be ok.

What's the catch?

Is it wrong if they are enabled side-by-side?

Yep, I'm having the same experience as @galambalazs above. I'm on a new macbook, el capitan, fresh install of st3 and markdownediting, and I kept getting this same error every time I restarted st3. I was able to stop the error by removing "Markdown" from the "ignored packages" of "settings -- user", and I no longer get the error... until I open a markdown file. Then the next time I close and reopen st3 I get the error again, and I see that "markdown" is again in my "ignored_packages" setting.

@rralian: you can safely ignore the error. This is because the default Markdown language that ships with ST3 was automatically disabled by Markdown Extended (this plugin), hence the presence of "markdown" within the ignored_packages.

If you're still having problems, have you tried installing Monokai Extended, and then enabling the new theme? See my commend a #108. This solved for me.