On 2023/09/27 17:56:34 +0000, Eponymous Pseudonym <suomyn...@gmail.com> wrote: > It's not only the display logic. Requires the text editor data > structure, file handling, buffers and mark, width re-flow, escaping > and probably other areas review and fixes too. Most of this is done > for the horizontal split already, but it's more than what the > horizontal (cut action direction) vertically (resultant panes above > and below the separator) split requires.
wow, wait, this is way more than I intended. All the points you mention can be surely areas where mg can be improved, but you don't need to change the buffer data structure, its file handling, or how dot/mark works to implement vertical splits. You 'only' have to augment the way the display draws the windows (emacs parlance for splits) so that they can be arranged in a tree (currently it's a list IIRC) to accomodate for nesting horizontals and vertical splits. Actually, we could take inspiration from the vis text editor and only split either horizontally OR vertically which is simpler. Re-flowing a completely different story. mg could do reflowing without supporting vertical splits or have vertical splits without reflowing; much like how a better data structure could reduce the memory footprint or allow some unicode support but it's independent from (much) of the display logic.
