If you are going to do interesting work on Leo and its plugins, you should be using Leo’s latest sources <https://github.com/leo-editor/leo-editor> from GitHub <https://github.com/leo-editor> using git <http://git-scm.com/>. Once git is installed, getting the latest version of Leo is easy:
git clone https://github.com/leo-editor/leo-editor.git Once you have done that, you can get the latest sources with: git pull Git is great in tracking history and reverting unwanted changes. And it has many other benefits. I've been wondering when to say this, but recent developments have forced my hand. Today, as the result of our Code Academy discussion, I have added the p.u property and a keyword arg to c.editCommands.deleteNodeIcons. If you don't use git you will quickly get out of the loop. Although git is unique behind the scenes, using git is very similar to using bzr or hg or any other SCCS. To change Leo, you add files, you commit files, and you push files. That's about it. I'll be happy to answer any git-related questions here. Again, I *strongly* encourage all would-be Leo programmers to use Leo's git repo. 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
