The way it is intented is to split the content, in a divide and conquer philosophy. This behavior is
in the core of Nested and in the way it process the document, so no, it can't. The tree contains the sections
of the document, you can move drag and drop, make child or sibling of any node (and in the future copy and
paste a whole section of the tree), quickly change the whole structure of the document, considering the sections
as nodes enables that. All this properties would be lost if the tree pane is just a dynamic index of the document.
Also, the tree should need to remember the line of the header it points, but any line you add to the document
modifies this, so a constant reconstruction of the index will be needed, one could be on any insert of a newline
or paste, which will be really hard for large documents, or an on demand by the user. In any case, this is out of
the scope and philosophy of Nested.
Thanks for trying the Software. I recommend you to use the development version, it as a lot of new features not yet
published: LaTeX log parser dialog, spell checking, custom LaTeX title and others.
If you're interested in programming this behavior for Textallion you can use the function body_to_sections() in nested_gui.py
exact behavior : viewer.py stores in the tree the line of an error or warning, both for the source document and in the log,
when the user clicks the error on the tree both textviews jumps and highlight the line where the error occurred.
Kind regards