I've been using Leo for quite a while now, and there's several things I like about it. But I've come to realize the main reason I initially wanted to use Leo, clones, is not really working for my use case. I mainly use Leo as a Personal Information Manager. My notes are organized in various sections -- but often I have items that belong to multiple sections, so I'd place them in both using clones. For example: a section with notes on Desktop software I use might have a subsection with Linux examples, but many of those are also relevant for under Webdevelopment - LAMP stack, so I'd put them there as well.
Now with over a dozen top-level sections and many more subsections and subsubsections for each, switching between different sections becomes unwieldy. The nav or search functionality works fine when you initially need to find the (sub)section you want to work in, but when you're switching between different sections/contexts a lot, the overhead is way too large (number of operations/keystrokes as well as mentally). Switching between open tabs works much better in this regard. So perhaps I should just make each top-level section a separate Leo file and switch between those? But as far as I can tell, there is no good way to share nodes between files (and keep them in sync, including their subtrees if applicable). Anyone organizing data like this, or have suggestions? -- 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
