On Saturday, April 10, 2021 at 10:12:42 AM UTC-4 TEK42 wrote: > Good find. That change works well for OS X too. Additionally, environment > variables can be handled: > ... > I've installed from the devel git branch, so I'll just go ahead and look > into how to contribute to this project. I'd like to enhance the "g.cls()" > also. >
For contributing, here is probably the best way. Set up an account with Github, then clone the Leo Github repo to it. Start by checking out the *devel* branch. The *master* branch isn't getting updated until an official release, so don't use that. In your clone, create a branch for the change you want, and make your proposed changes. Then in the Pull Request tab at Github, create a pull request. You could do all your work in a virtual environment, but I like to set PYTHONPATH to point to the top of the repo instead. Then Python will find Leo in the repo but all other python packages from their usual places. On my Windows machine: set PYTHONPATH=d:\tom\git\leo-editor python3 -m leo.core.runLeo One advantage of doing it this way is that you can run the ordinary Leo release simply by unsetting PYTHONPATH. You don't have to try to remember which venv has got which configuration, or how to get the venv to use the repo. I've learned that it's best to make a new branch for each of your change projects, no matter how small. Once the PR is closed, you can update from Leo's *devel* and again branch off it for your next effort, or merge your branch back into your clone of *devel*. Of course, you may be way more experienced at doing the PR dance and if so just keep doing whatever you have been doing! -- 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/b2a53dd6-8cbb-45b3-9866-7cdfda4d133fn%40googlegroups.com.
