On Tue, Sep 20, 2022 at 11:52 AM Thomas Passin wrote:
> I'm missing some essential piece of understanding, I think.
>
> 1. I work on an existing external file (this is mostly what I have done).
> This probably won't change LeoPyRef. I commit the changed external file
> but don't commit
I'm missing some essential piece of understanding, I think.
1. I work on an existing external file (this is mostly what I have done).
This probably won't change LeoPyRef. I commit the changed external file
but don't commit LeoPyRef. I don't see this as needing a leoPy.leo outline
at all.
On Tue, Sep 20, 2022 at 11:29 AM Thomas Passin 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.
I'm confused about leoPy.leo vs LeoPyRef.leo. Some time ago, things were
changed so that opening leoPy from the File/Open Specific Leo File menu
actually opened LeoPyRef. There is no leoPy.leo in the leo/core directory
any more. Looking through the write-leoPyRef, I infer that we are
There is an ongoing problem with the script `@button write-leoPyRef`.
Iirc, this script is intended to be run from a dev's local leoPy.leo file.
There is a big glitch. After running this script Leo's git-diff command
reports minimal changes, but actually loading and saving LeoPyRef.leo
creates
