Hey: I really bet Leo can do that. Since Edward is currently updating the tutorials to a new level, probably your question can be translated into a "new tutorial".
I dont know how to answer your problem (even though Im positive developers will have a solution for that). But with your question you cover some issues I still don't clearly know, and I think a new-fashioned tutorial about the topic would greatly help. Here is the general outline I would answer in such a tutorial, which I would address as *General File Managing with Leo*: - Tell the user to create a @auto - then clone it - Then edit the original file - Then refresh from disk - Explain what happened with the file (the why is not so important, we just want to know how it works, not why, so we can keep this short. The "why" should go in the main tuto) - Tell the user to create a @thin file - Same steps, but just different explanation on what happened, such as "the clone was updated to do XXX". - Same with Leo file directives. With those, we would easily know how to expect Leo to behave when we interact with its files structures, instead of having to spend time testing by ourselves. -- 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
