Hello Edward! Thanks for these comments. @clean can help, but perhaps not as much as we > all would like. > Another pain of using LEO as a replacement of IDE is that all the code you store in @clean is duplicated, which pollutes git alot. So I still dont know what is more evil - @file or @clean.
> > The upcoming "Leo for vs-code" plugin (the leoInteg project) is likely to > solve most of the problems you mention. Vs-code will give you the > typical/traditional view of all external files, while the "Leo for vs-code" > plugin will give you the Leonine view. > Actually I love original LEO's gui, even it has some very major disadvantages, and would be missing it. But also I understand that it becomes very painfull to implement new modern features for it. So waiting vscode plugin with hope. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAC%2B8SVwycJBYkcAMu5JaKdUOuyrmiCn2NhQdyAQEPnCxgis2zg%40mail.gmail.com.
