many (most?) problems with imports can be fixed by hand in the generated > @clean tree.
Yes, I am aware of this. But it turned out quite often for me that amount of work needed for that manual fixing exceeds the amount of work needed to split file by hand in the first place. I would not argue that files from some (possible many) other languages can be imported properly. But there is not so small number of languages like javascript which can't be imported satisfactorily. Javascript itself has a number of dialects, scala is another example. Groovy also comes to my mind. They have so rich syntax that I really doubt that Leo in its current form can handle them very well. I haven't tested it, but every time I used import I ended up doing lot of manual reshaping and quite often I abandoned the whole process and started all over again with manual splitting file. Vitalije -- 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.
