Hello (with question about contributions)

[Przemysław Kamiński (XLII)]

Hi,

I recently recently re-discovered Leo. Previously I couldn't make it to work for me, but now, with some LLM-aid I was able make it look (and behave! ;-)) to my needs. I have a soft spot for quirky outliners and complex software, yet I cannot say I'll stick to Leo. As of today it's fun to mess around at least.

As stated above, I'm changing Leo if something doesn't work for me. So far I:

- fixed macOS specific bug in which <save-file> was targeting wrong file (because of menubar sharing, it just picked one and saved it over and over again no matter focus)

- made a `uv` - based macOS App builder (with a nice - according to myself - modern icon and read-only settings/quicksheet files to prevent accidental destroy)

- added setting controlling whether swap Command and Control (on by default, found it infuriating)

- looking at why <reload-settings> doesn't reload keybinds (and it seems that because it don't and that's it)

I'd be happy to share any changes I make through PRs, however I have absolutely no idea how Leo is developed and if such straight-to-the-door approach and PRs themselves are welcome or not. I completely understand that some projects, even when developed in public, don't accept unsolicited changes - thus before doing so I decided to ask.

I need to put a disclaimer that I do use LLM to aid with development. I'm not a huge fan of Python so would rather not write it. But with LLMs it's much easier. I review code, though more as a language-agnostic engineer with experience, and not as a Python focused one. There's my head in code/work, but the fact of LLM being there too - remains.

Best,

Przemysław Alexander Kamiński

[Thomas Passin]

Hi, glad to hear from you. Anyone is welcome to file an issue or contribute a PR to be merged.

The best way is to first create a new issue on Leo's GitHub site. Mark the issue as a bug if that's what it is, and a proposed release version for the fix, using the selections at the right of the GitHub window. Otherwise it may get overlooked for some time.

If you want to contribute a PR to fix the issue, it's best to clone the Leo repo and do the work in a new branch in your clone. When you submit the PR through GitHub, target it to the "devel" branch. Please identify what an LLM has contributed if it has.

Code files should be "@file" trees, not "@clean" or any other alternative. You can see how that is accomplished by looking at any Python file in the repo. Leo is advertised as being backwards compatible to Python 3.10, so don't use any features that don't work as far back as that.

Someone, most likely Edward [Ream] will review the PR before merging it or asking for changes.

Please be aware that Edward is moving towards using fairly strict type annotations for Leo. So new PRs should try to include type annotations, and will be checked using mypy, pylint, and flake8 at least.

There is a test suite and scripts that run it. Make sure that your PR doesn't add any new test failures.

Of course, ask for help about anything as needed. 

Help with Mac-specific issues will always be welcome since I don't think any of the main developers have a Mac, and certainly don't have many Mac skills.