[KevinH]

Hmmm ... split at cursor is handled almost entirely within CodeViewEditor.cpp code with some help from Book.cpp, where as "split at markers" is handled completely outside the file or editor as it is meant to be recursive and possibly apply across multiple files.

I will look into this but there will always be some nested structures that will not survive splitting at certain points when using Split at Markers as opposed to splitting only once inside of a file using Split at Cursor.

To be safest, split at marker split points should be chosen by the user to be a direct child of the body tag. In this case the split at marker is a direct child of the div which typically indicates that this block should not be broken there as div are used to physically and logically group things. Ie. you typically want to split the body into multiple parts.