On Tue, Jul 5, 2016 at 12:46 PM, Propadovic Nenad <[email protected]> wrote:
> there seems to be a big gap between those who dig it and those who don't, > and I seem to be on the don't-dig-side. Not the fact that it can be useful, > but the fact that ut can be useful to extents that it has some fanatic fans. > Leo isn't for everybody, and that's completely ok with me. > I tried using Leo for tasks that jumped at me, like, translating some code > from Perl to Python. I did it by analyzing the (very poor) structure of > that code in Leo, and it still took me a week; afterwards I realized I > would have been better of, if I had just translated it to Python - command > by command - , *without* understanding the structure, and *then* tried to > force structure upon it; so decomposing and analyzing seems not be the > right method for this kind of task. > Leo can't create structure out of nothing. Your experience is what matters. Now you know at least one limit of what Leo can do. > Now, again, another task: I'm analyzing some Python code, much better > structured. Still, it's quite complex, the state-machine it contains has > multiple rather unclear transitions and conditions of changing > transitions... Leo helped me only so much, but just the implications of > this and that changing value in the code at runtime... is just not yet > clear to me. Trying to analyze seems to be less useful than adding log > entries to see the runtime values. > This is often true. I use g.trace often to understand other people's code. @clean is especially helpful, as is using git. That way, git diff will show me exactly what I did. > So, after seriously trying to use Leo for tasks that came along my way, > and finding it nice, but not so useful that I'd say it's indispensable, may > I ask: what are you guys using Leo for? > I use Leo for understanding code. And that's about it. > I realize that writing code of the size and quality of Leo itself is a > huge task, and would be hard without a good tool; but are there smaller, > but also very useful things you can do with Leo, which would be much harder > without it? > I'll leave that for others to answer. > (Yes, I have read the documentation; not I have not *studied* it). > I'd appreciate examples which *show* me why Leo is great. > You will have to answer for yourself. It's ok if you don't want to use Leo. 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. For more options, visit https://groups.google.com/d/optout.
