On Jan 4, 12:07 am, Matt Wilkie <[email protected]> wrote: > > 2. I am not aware of any "painful" bugs that would afflict newbies > > "right out of the box". Excepting on MacOS, which is not truly > > supported, and perhaps never will be.
I have started using leo seriously maybe just 2 months ago, and *EVERY* time I got a bit creative with applying clone nodes and other advanced Leo features to my workflow (managing JSP files using @shadow nodes, sometimes I edit the files in Eclipse as well), I really ran into "lost data/leo crashes/unreadable files" kind of bugs. I was able to report few cases here, but I have no doubts there are many more problems. If Leo would not be so helpful, I would abandon it. Instead I have learned my ways around and have postponed any testing of clone nodes after I finish current work project. Overall, I have got feeling that Leo enthusiasts are using it mostly for their own little Python development or creating documentation. Support of other languages or @shadow nodes (to cooperate with people that don't use leo) feels more like experiment. For example, Leo *never* asked me about conflict when saving or reading @shadow file. At most it just spits out useless "uncached read node changed" messages. I always have to remember myself whether I have changed file on disk so that I need to reread it, and vice versa. It feels like a rant, sorry. But I have to disagree with whole "Leo *is* stable, 99% of the time or more" premise. Maybe it is, if you 99% of the time don't disgress from your workflow or don't have to deal much with changing external files... Juraj -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
