Over at language-markdown we have been discussing (just a little, we know it is silly to argue about it) what our base scope should be, and we decided on text.md. We have considered using text.markup as it is more semantically correct, but text.md seems to more closely follow existing conventions.
Anyway, from our personal experience, we often use Markdown as an ad hoc or more organized todo-list-tool. So we'd like to suggest adding both 'text.md' and 'text.markup' to the injectionSelector of this package for that purpose.
Over at language-markdown we have been discussing (just a little, we know it is silly to argue about it) what our base scope should be, and we decided on
text.md. We have considered usingtext.markupas it is more semantically correct, buttext.mdseems to more closely follow existing conventions.Anyway, from our personal experience, we often use Markdown as an ad hoc or more organized todo-list-tool. So we'd like to suggest adding both 'text.md' and 'text.markup' to the injectionSelector of this package for that purpose.