Dear, Edward K. Ream, I believe your daily workflows is an invaluable asset, as well as leo-editor.
Even the doc and Leo files contain lots of information there, but there are still lack of your workflow of Leo. For example, in doc Lesson 7: How to make complex changes to a code base <https://leo-editor.github.io/leo-editor/leo-university.html#lesson-7-how-to-make-complex-changes-to-a-code-base>, I still don't understand how and where to set a *global master switch*. For this case, there maybe someone tell me how to do this, but I think we can understand this easily by see your video. Another example, how to use g.trace, g.gdb, I think few people can master it. But maybe through the video, we might be able to have a certain understanding. Don't get me wrong, I didn't mean to add extra work to you. You have given us such a precious Leo, we couldn't ask for more. I just think that for some bugs/features with a small workload, how to fix/add them and how to observe your daily operations are worth recording while you are working. After all, you are the only Leo editor master. For some knowledge, we can't get it from text. Just like riding a bicycle, we can't really learn it by reading books about how to ride a bicycle. We need to practice, we need to see how other people do it. Best, HaveF -- 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/0e612cf1-0246-4b00-ae1b-68297ef47b30n%40googlegroups.com.
