On Tuesday, April 11, 2017 at 6:55:56 AM UTC-5, Edward K. Ream wrote: >> There is a better workaround, namely, use a separate local leoPy.leo for each branch: > This workaround is probably good enough for the foreseeable future.
Rev b32259 appears to fix #385 without the need for any workaround, simply by adding the branch name to the hash used by Leo's caching code. As a result, Leo loads all necessary files from the new branch. This is an elegant and simple solution. 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
