Thanks for advises! I am still learning to use Leo in a proper way. I was told that learning curve is too long ans steep. But now it seems that it worth of it.
I'll take into consideration all those things you mentioned about. I am already familiar with chapters and they do really help when you deal with huge tree of something-that-looks-like-a-book (like my PhD book which I am trying now to move to Leo from bulk of bookdown Rmd files). Searching/finding is not very popular feature for me now since I do a lot of dummy copy-paste work, but later I'll try to remember about clone-find and quicksearch. Actually what I've discovered... When you face a new tool - first you try to use it in an any familiar way. Say you were using Notepad++ for years, and then you ought to use vim. What would I do? I would try to understand how to get red of all those silly commands and bring back my habitual Notepad++ features (yeah, that's my true vim story....). With Leo I tried quite the same. And that was a mistake. I think that I should pay more attention in learning the paradigm. Read more docs, try to write a couple of plugins. For now I need a tool to build my book from Rmds - maybe it'll be a good challenge to write such a plugin which would connect Leo, bookdown and R. Thank you all that you help novices with advises :-) I do really appreciate it a lot. The community is small but very friendly. четверг, 27 июня 2019 г., 23:09:51 UTC+3 пользователь john lunzer написал: > > What a great revelation, and a perfect example of how an editor can shift > the paradigm of editing. > > Make sure you look around for the different ways of searching through and > managing larger outlines: > > - The "clone find" family of commands > - I find Chapters to be a nice extension of the tree hierarchy > - The Quicksearch plugin is great for quick searches... no really it > is. > > > On Thursday, June 27, 2019 at 11:15:57 AM UTC-4, gar wrote: >> >> After several days w/o vim mode I understood the dao of leo. >> There's actually no need in vim mode at all. >> >> Vim editing style is good when you deal with thousands (ok, hundreds) >> lines of text/code. >> Then is boosts your alot. >> But when you edit small text/code snippets - there is no difference what >> editing style you actually use. Any is ok. >> Your responsibility is to make suitable hierarchy and keep node texts >> reasonable small - and then the problem of editing wont even arise. >> When you edit a couple of paragraphs - all those modes and switches >> become obstacles! >> >> So there's no real problem that vim mode is dead in Leo. As I thought >> just yesterday. >> >> >> >> понедельник, 24 июня 2019 г., 14:01:41 UTC+3 пользователь Edward K. Ream >> написал: >>> >>> >>> >>> On Mon, Jun 24, 2019 at 4:11 AM gar <[email protected]> wrote: >>> >>>> It is totally unusable unfortunately >>>> >>> >>> Thanks for this report. Perhaps you can help improve the vim plugin. >>> >>> 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 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/f649c35e-3627-4aa7-9326-de21da15e02d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
