On Thu, Aug 1, 2019 at 12:30 PM john lunzer <[email protected]> wrote:
Everything in emacs exists within a "buffer" which is really just text > windows. > Everything in Leo is an outline, consisting of true Python objects, not just plain text. While each of the proposed emacs feature is nice, they would become truly > powerful if they are well integrated into Leo's tree/node paradigm. > Actually, Leo uses emacs's named commands. So for instance, implicit in all proposals are the addition of Leo commands. For instance, pyzo's file browser does what dired does. But I'll add emacs-like commands (dired-*) so that everything the file browser does can be done a) via a keyboard shortcut or b) via a script. > For example I see a reasonable implementation of a Jupyter console as > creating a node name "@jupyter my_console" which could then be "activated" > or "run", generating a child node named "In [1]:" after the jupyter kernel > booted up and was attached. > We can discuss this later. For now, I'm happy to use the pyzo code as it is, with the addition of emacs-like commands. With Leo's current body node capabilities the above interaction might be a > little cumbersome. However, if Leo had a vertically sequential multi-node > body pane (which I mocked up about a month ago) this interaction would be > seamless. Being able to save the "@jupyter my_console" sub-tree and move > it's children around would have great utility. > See #1228 <https://github.com/leo-editor/leo-editor/issues/1228>. It's too early to tell how this will fit into Leo. The active_path.py plugin already kind of implements dired as a tree, but > it's pretty rough around the edges, > Pyzo's file browser is superb. If different types of "@directive" nodes could dynamically alter the visual > style of the child nodes displayed in a multi-node body editor you could > for example make the body appear to the left of the headline and remove any > upper and lower borders and spacing for children of an "@dired" sub-tree . > In this way the sub-tree of "@dired" would look almost exactly like an "ls > -l" listing. With the exception that it would *still be a dag/tree/nodes > all the way down*. In the same way you could style the children of an > "@jupyter" node to make the visual look and feel of a jupyter notebook. > Pyzo's file browser could display ls-style listing in an optional "nerd mode" ;-) All of a sudden you have powerful tools that look and behave exactly as > people are familiar with but are also true Leo trees. > That's not my goal. If people want emacs, they know where to find it. > Now try to imagine these features with Vitalije's time machine feature. > Leo would undoubtedly be one of the most powerful computing tools in > existence, surpassing the might and utility of many other tools/IDEs > combined. > Leo already is that ;-) Edward -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS3q_Jq%2BgzFvfJFDFewOFckcQ_y6%3DxDdvRZgQMD9gtJ%3D-Q%40mail.gmail.com.
