SUMMARY It would be hugely useful if one could enable Table of Content (TOC) in Kate for text documents such as txt files or files without filetype. This would make it easy to structure / sort notes, todos and other texts into separate sections. There would need to be a syntax for the headers of the sections. This could be configured or changed by the user. The text has the syntax "Normal" (this should work with default settings when simply opening a txt file). I don't think Kate currently can display a TOC even if the file has Markdown set as language. There could be a small input box where you can easily quickly enter the characters that create a header. This could look like / work like the input box that open when you click on "Line x, Column y" in the bottom left. You could enter something like "####" to make this the default string that's used for headers. If you then write "####This is is a header" somewhere in the txt document, it would (or just "could" with whether or not depending on your settings) display just like all the other text in the file (no color-highlighting or headers that have a larger font-size) but still make this show up as a section in the TOC. The TOC would be shown in a panel on the left, like or included in the "Documents" tab that can also be shown there if you have multiple files open in Kate. Clicking on a header would jump to it in the text file. Can't overstate how useful this could be. STEPS TO REPRODUCE 1. Use Kate to write down notes 2. Do this until notes grow long 3. Try to organize things into separate sections, not just separate files 4. Try to show a TOC for the sections by which you structured the documents OBSERVED RESULT No TOC can be shown. EXPECTED RESULT A TOC can be shown that takes up little space and is located somewhere in the panel on the left without having to switch between the Documents tab and a TOC tab (both are visible at once). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian 11 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION
*** This bug has been marked as a duplicate of bug 376480 ***