-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple TOCs in the MD #51
Comments
Thank you for your suggestion. I already list up this feature at #15. I think an issues will arise in your way. It's something like ...
The problem is that the first TOC will include 'SubSection' in next 'Section'. I prefer adding content start tag and end tag each toc rather than adding level range.
But I think your 'level range' idea is good for another way of use. So, I list it up as another feature. |
Modify around this line. |
Hi. Thanks for the great plugin. It is very useful to me. I'd like to make a feature request.
It would be very useful to be able to have multiple tocs. When I insert one toc it shows the headers after the place the toc is inserted. This is very useful. But I need to be able to insert multiple tocs. The use case is this. I have some pretty long documents (javascript api docs). I want to have toc at the top and then toc for different sections. So on the top the toc won't be mile long and when you go to a specific section you can navigate to the subsections. Right now I achieve this by enabling full depth of the toc headers in the config and then I copy-paste manually from the main toc to the sections. Needless to say I have to keep track manually and update all sections when I change them.
And this brings me to the second part - it would be very useful to be able to specify options per TOC. The options that normally go in the sublime config like
"default_depth": 6
. I imagine something like<!-- MarkdownTOC 3-7 -->
which would mean "generate toc here for the headers level 3-7 starting from this point of the document". This way one can maintain sections easily.Regards,
Bobi
The text was updated successfully, but these errors were encountered: