On Tue, Sep 20, 2022 at 11:29 AM Thomas Passin <[email protected]> wrote:
Looking through the write-leoPyRef, I infer that we are expected to create > a leoPy.leo outline - presumably by saving LeoPyRef by that name, doing all > our work in leoPy, then using the write-leoPyRef command. Is that the idea? Yes. Why isn't it OK to just work with LeoPyRef, and avoid all the headaches of > diffs because of changed gnxs, etc? > gnx's aren't a big problem. What we want is to avoid git merge problems with LeoPyRef.leo. Local copies (leoPy.leo) should avoid most git conflicts. Edward -- 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/CAMF8tS01eG87r2P1DMj9G9%2BQCw4CYYrehbbP9QsYmk%3DbK4u_FA%40mail.gmail.com.
