On Wed, Sep 3, 2014 at 5:25 AM, Edward K. Ream <[email protected]> wrote:
> P.S. git and easier access to pylint contributed to the present avalanche of > energy and ideas. Another seemingly small, but actually very important factor is my new practice of immediately testing changes on ubuntu. Except for drastic changes, like the ones I am presently doing, I typically do the following: 1. I skip unit tests on my slower Windows machine. I do, however, open a small test file to ensure that Leo doesn't crash on startup. 2. I push without complete testing, and then immediately pull on my much faster Ubuntu machine and run the unit tests there. This work flow pretty much guarantees that Leo will work on Windows and Ubuntu at all times. When Leo does fail to load on Ubuntu, the problem can be correctly immediately. I've written this up before, but it's worth repeating. At the (small!) cost of possibly pushing something that will break on Ubuntu, I now have much more confidence that Leo is solid at all times. The result is *much* more energy, especially when doing wild and crazy things as at present. EKR -- 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
