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 huge diffs as far as git itself is concerned. I'm not sure what to do about this. Rev be3e404c in devel contains what I think is the latest version of LeoPyRef.leo, with the big diff. This "round trips" properly: loading and saving LeoPyRef.leo creates a "null" diff (except for whitespace.) *Summary* My inclination is to leave everything alone for now, with the understanding that the new procedure should be: - Run @button write-leoPyRef. - Use Leo's git-diff command to check the "logical" diffs, ignoring node placement. - Load LeoPyRef.leo and save same. - Use the actual git-diff to double check the "real" diffs, which should be minimal. - Commit LeoPyRef.leo if there is a non-trivial real diff. Your comments, please. 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/339390a0-4177-442b-bcd8-fd1d1ae3f021n%40googlegroups.com.
