I just noticed that the TOC for Markdown files does not show all of the headers in my file. The only workaround I have found to I force the headers to show in the TOC is to files to insert the code in the line just before the header hashtag. The header in the document looks just fine. Is this issue being addressed? Any other tips until the issue is resolved?
Can you show an example, please? Code and screenshot of the TOC
Is this issue being addressed? Any other tips until the issue is resolved?
There is no known issue to be addressed so there’s no timeline for it to “be resolved”.
1 Like
Bluefrog. The headings render just fine in the document. Their appearance in the document match the hashtag font size, but they just don’t all show up on the document TOC
Screenshot
I don’t know what this TOC is related to. Please see the post of @BLUEFROG for usage of the {{TOC}} code in MD documents. And possibly also checking out the documentation on the inspector TOC
It also looks like the TOC the OP is showing has disclosure arrows beside the entries that are showing. My bet is that the missing headings are there if you click the chevrons.
4 Likes
Two lessons learned (again)
- when two people use the same term, they don’t necessarily mean the same thing.
- Sometimes it can be so easy if one just looks
Thanks!
1 Like
Yes, headers of different levels create a hierarchical structure that can be expanded and collapsed. By default they are collapsed. This is useful for navigating long documents with many headings. It works the same in PDFs.
That’s it! Thanks for all of your help. And sorry @BLUEFROG for reporting this under “bug”. Humble Pie for me, again! I clicked the disclosure arrows on the TOC headings and the hierarchal structure of all of the document heading showed up. And the links to the document worked fine. And I found reference to it in Help when I searched “Table of Contents” Help>Inspectors>Content>Table of Contents Thanks to all,
4 Likes
You’re welcome 
Some additional tips that may be useful here:
- Standard outlining keyboard shortcuts are supported in the Table of Contents inspector: right-arrow to expand the selected heading, option-right arrow to expand all subheadings, left-arrow to collapse. Last viewed expansion is persistent, i.e. previously expanded subheadings remain expanded after a parent-level collapse and re-expand. (Apologies if that last bit is incomprehensible to any but outliner-heads like @Amontillado.)
- Items in the inspector can be dragged vertically (but currently not horizontally; to change levels you need to edit the #s in the Markdown edit pane).
- The Inspector can be drag-resized to fill up to half the window, giving you an unusual but very effective two- (or three-, using split view for the main window) pane view with editing functionality in the left (Markdown editor) pane and an outliner view with vertical drag-to-reorganise in the Inspector pane.
- Bulleted paragraphs (MD prefix hyphen-space) will display in the Best Available pane but will be hidden in the Inspector.
- Text paragraphs terminated with a double space will display as paragraphs in the BA pane but will be hidden in the Inspector.
The combination of these features is a really big deal for anyone who’s been craving a proper outliner for Markdown, something that has yet to be satisfactorily implemented anywhere. Though not intended as an implementation of a MORE-style dedicated outliner, the DT4.x feature combo has been proving powerful and versatile enough to be gradually pushing Scrivener and Ulysses out of my default longform writing workflow towards the utopian convergence of doing every single possible thing in DT, with the exception of sleeping, eating, and brushing your teeth. (@cgrunenberg: “These features will be implemented in a forthcoming release.”)
5 Likes
Just when I thought today would be a total loss - I’m honored!
2 Likes