> > Whilst there is a benefit to the "focus" of seeing only one node at a > time, in the cases where I use Org-mode I explicitly want/need to see > multiple nodes at a time.
This is something I would really like to be able to use in Leo. Both for writing text as well as code, being able to see the preceding and following node contents would be very beneficial. In my opinion there are a few important drawbacks to the current situation: 1. There's a need to hold a lot of the context in your head (e.g. how did I start the previous paragraph? What function name did I use in the parent node? Etc.). This takes up space in working memory. 2. When it's urgent enough that you need to look up this context, it takes several key strokes, plus you lose focus on the position where you were working. If you can just scroll up or down to see this context, without having to navigate and maybe fold nodes, then scroll back, you do not lose the visuo-spatial sense of where you were, even if you'd scroll the selected node out of view. I.e. you remember how much scrolling you'd have to do to get back. At least that's how it works for me. 3. Because of 1 and 2, I tend to avoid creation of more fine-grained nodes to structure my work, even though it would otherwise be beneficial. I found a few places where this idea was discussed before: Feb 2017 https://groups.google.com/d/msg/leo-editor/qkcmQGL7fdw/l3DvLAoVCgAJ Sep 2017 https://groups.google.com/d/msg/leo-editor/7OANSWcoOzg/b_tXlLTzAgAJ "multi-pane editing" Cheers, Arjan -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/a6b8ec16-1cb7-425d-95bc-df18c0d21beb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
