New plugin: MarkdownCodeExporter - Should it be merged here as well?

[maliayas]

I've created a new plugin named MarkdownCodeExporter (not pushed to Package Control yet) that's related to SublimeText and Markdown. So it belongs to this GitHub organization by definition.

I'm planning to keep it as a separate plugin for those who don't use MarkdownEditing. But at the same time, it's functionality can be merged into MarkdownEditing because that would make a lot of sense for MarkdownEditing users. And with a config key like mde.feature_disable.code_exporter it can be easily enabled/disabled.

Do you think it should be merged here?

[deathaxe]

If it exists as separate package there's no requirement to duplicate its functionality here.

[maliayas]

If our existing users won't notice the separate plugin and if they would happily use it if it was merged here then I wouldn't consider that duplication an issue.

But allright, I see your point. Then once #781 is resolved this plugin can be advertised in a "Tips" section of a document for the benefit of our users.

Cheers!