Add Markdown Table of Contents package

[codeleventh]

• I'm the package's author and/or maintainer.
• I have have read the docs.
• I have tagged a release with a semver version number.
• My package repo has a description and a README describing what it's for and how to use it.
• My package doesn't add context menu entries. *
• My package doesn't add key bindings. **
• Any commands are available via the command palette.
• Preferences and keybindings (if any) are listed in the menu and the command palette, and open in split view.
• If my package is a syntax it doesn't also add a color scheme. ***
• I use .gitattributes to exclude files from the package: images, test files, sublime-project/workspace.

My package is prepending Markdown files with inline Table of Contents

It adds own keybinding (Ctrl+Shift+M)

There are no packages like it in Package Control (that's why I did it, lol).

[braver]

There are no packages like it in Package Control

How about https://packages.sublimetext.io/packages/MarkdownTOC?

[braver]

It adds own keybinding (Ctrl+Shift+M)

It looks like this package should just work fine without that. Please comment out your binding, and let that just be an example for users to set their own. That way you're sure it doesn't clash, and users can pick something that makes sense to them (and their OS, e.g. on MacOS you'd usually pick cmd instead of ctrl).

[kaste]

Looks wonderful. If I click a heading, it closes the phantom; otherwise it updates them while typing. I think you should keep the table open on click. There is a setting for that already.

[codeleventh]

@braver, yep, I've removed the excessive fields and default shortcut key.

About MarkdownTOC plugin: it's purpose is different — it's for modifying the document for the reader's convenience. This plugin is for the author's navigation within the document.

[codeleventh]

@braver, any chances to merge this?

[braver]

It's on the list of things to look into. We do have a schema test issue here. Not related to your package per se, but I need to double check that before we merge.