Hello Chris, Viktor, You and others have brought up great points about how Leo is used in a day-to-day basis. I'm having trouble with what appears to be "one" editing window.
Please, correct me if I haven't figured this functionality out yet. Namely, I appreciate 'Tabs' and appreciate that leo itself has a number of tabs that refer to 'the whole .leo document' loaded. I can have numerous Leo files open; but I cannot seem to get multiple edit window views on multiple nodes at once. This sort of functionality can potentially be brought about by embedding in some scripting (im not quite sure how/where) that would automatically launch a brand new SublimeText project, and then iteratively 'add' new files, potentially autocreated per my previous queries here, to this SublimeText session... and then remember to somehow make sure Leo gets them updated back into itself. What I would love, is to embed sublimetext as the text editor widget. Somehow. It would let me have tabs for every edit view i am working on at a time (manually openable, closable, not precisely 'all potential nodes auto-opened' as I can only imagine to do it now so as to have some semblance of a 'session of files to be saved upon exit of Sublime' - which then would get reloaded into the .leo file. It would allow me to drag a tab into a brand new window if I wanted; multiple windows with 2-3 tabs perhaps, different from the others, as sections of 1 leo file. Then Leo should allow me to close it, and then all the sublimetext editor window session bits get saved like Sublime already does, without me having to hack on not just my own .leo file customizations, but also the autosave script itself to 'not care' where I am in the interface; i am often _not_ in the editor pane when I am wanting my last changes whilst in the editor pane to save; i've found some limitations to the speed of some of my computers with regard to saving the file every second, to 'hopefully' save before I've moused out of the text field... But I found editing the autosave plugin source to just not care what context its in, to work 99% of the time and only cause me to screw up typing node-names sometimes if i'm not quick enough. but 5 seconds is really long enough to edit a node name before the entire view redraws as it saves. So this, is both a workflow and a logical 'things should just automatically save, and be remembered later' desire. I cannot explain how frustrating it is to me to exit out of my desktop after having ssh'd into a large number of things i work on daily, with their terminal histories, and all related content to be lost. I can save my browser history; i can save my browser form content; i can expect sublime text to automatically save and remember itself when it relaunches. I cannot expect the same level of autosave / "state remembering" granularity of resuming with Leo. And this is a sad problem to have, for all of its benefits of organization. Truly for organizing, it works great.. But for me, I use this state-remembering of Subl3 all the time. I use its tabs, all the time. I use its relatively complete 'vi' mode all the time, and appreciate how it interacts with the common sublime and other ui "ctrl-c/ctrl-v" concurrently with vim 'command-mode' commands that I am accustomed to. It's truly the best of both worlds, "gui" and "vi-style" text editor all in one. And Leo's interaction with it, and with the types of text files I am using in general, to display the text in an editable, auto-completable, manner, is not so good. So I might appreciate an editor plugin 'of leo'... But really I'd appreciate a replaceable/embeddable text editing widget far more. Thanks, Mike On Mon, Aug 29, 2016 at 1:02 PM, Viktor Ransmayr <[email protected]> wrote: > Hello Chris, > > Thanks for starting a new thread & sharing your perception. > > My initial feedback: If Leo (as is) fulfills all of your needs, then that's > a good/ great status for you! > > Another feedback: IMO a lot of the discussion focuses on the questions: > Should more things be added to the Leo environment (the Application, the > IDE, the Outliner, the PIM, etc.) - or - can (must?/ should?) the experience > from Leo's past & presence be used to extend other communitie**s** & > environment**s**? > > I'm repeating myself: I always understood the original contribution from > 'tfer' as an input for the later one ... > > On Mon, Aug 29, 2016 at 4:34 PM, Chris George <[email protected]> wrote: >> >> Over the past couple of years I have begun to see Leo as an outlining >> editor that can emulate every editor and every outliner out there. Every >> time I try to narrow Leo's spot in in my toolchain, it widens and another >> dedicated tool passes on. >> >> The recent discussion about paring Leo down to a plugin for a text editor >> really brought this into focus for me. I think what users are looking for >> here is a Leo where the text edit box looks and acts like their editor du >> jour. Focusing on learning markdown and restructured text really focused me >> on how little I need to learn and how unimportant formatting WHILE writing >> fiction and non-fiction truly is. >> >> What wins are the words. The writing is organized. Leo makes sure of that. >> >> So after all this time, I load up a different editor for evaluation >> (Visual Code, which seems to be atom designed by grown-ups) and find myself >> missing Leo's text box, my abbreviations and my organizer file. Now atom or >> code becomes the whizzy plug-in material for Leo to wrap. But at that point, >> why bother. Why not just emulate as was done with vim? Any tool that would >> or could be classed as outliner or editor can be emulated by Leo. >> >> So why bother writing new editors when you could emulate one in Leo? >> >> Pondering onward, >> >> Chris >> >> -- >> 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. >> For more options, visit https://groups.google.com/d/optout. > > > -- > 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. > For more options, visit https://groups.google.com/d/optout. -- 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. For more options, visit https://groups.google.com/d/optout.
