Re: Why I want to blacken most of Leo's sources

I'm happy to have black available and used by default. I know all of my own stuff could use it. I tend to constantly switch between single and double quotes without much rhyme and reason, so normalizing would be good. Somewhat related is *isort* - https://github.com/timothycrosley/isort, for

black branch merged into devel. Work continues in the black branch

This merge completes the primary work on #1272 . This issue creates four new commands: - The black-diff-tree/node commands print diffs to the console. They do not actually change code. - The black-tree/node commands actually change body

Re: Why I want to blacken most of Leo's sources

On Thu, Aug 29, 2019 at 12:28 PM Terry Brown wrote: Normalizing quotes is actually the one thing I don't have black do. > I didn't remember that that was a black option. In that case, it should be a Leo setting as well. Edward -- You received this message because you are subscribed to the

Re: Work on pyzo_in_leo will continue in a day or three

On Thu, Aug 29, 2019 at 2:25 PM Robert Cholette wrote: > What is blackening? > It's to reformat code using python's black code formatter. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe

Re: Work on pyzo_in_leo will continue in a day or three

Sorry i've been away from leo's forums a bit...cant help but ask: what is blackening? On Thursday, August 29, 2019 at 12:53:37 PM UTC-4, Edward K. Ream wrote: > > Yes, we are all impatient :-) However, there are some urgent tasks to > attend to first: > > - Fix #1307

Why I want to blacken most of Leo's sources

This is Leo issue #1272 . Don't panic: blacking *your* code will always be entirely optional. A setting will specify where black breaks lines. I'll probably use the suggested default, 88, but if you do decide to use black, you can pick your

Work on pyzo_in_leo will continue in a day or three

Yes, we are all impatient :-) However, there are some urgent tasks to attend to first: - Fix #1307 : @first/last invalid in @clean trees. - Disentangle #1266 and #1272

The gui branch has been fully merged, and deleted

This is another administrative convenience for me. I have declared #1289 : global, singleton docks, to be complete. Don't panic! We'll continue our examination of "artifacts" in global docks while working in the pyzo branch. Edward --

pyzo branch merged into devel. work continues in pyzo branch

Merging pyzo into devel is a convenience for me while work continues in the pyzo branch. The changes: - The --global-docks command-line argument no longer ever creates dummy global docks. - The pyzo_in_leo plugin is functional, modulo well known bugs. It creates all of pyzo's global docks. -

Re: Discusss: use Discourse instead of mailing list

Hi, The idea of using another platform, instead of mailing list, has arrived locally from time to time. FYI we have considered NimForum[1] because of its simplicity and because we would like to deploy and migrate data in an easy way in case of being necessary. But for now, we still keep the

Re: Question about running / driving leo 'headless' to integrate it in my own GUI

Thanks! Now that I've reached this milestone I'm going to cleanup/refactor the code : The js (typescript) part is not too bad, but the python side has no classes (just functions and globals) so this needs a little organisation! Then next (maybe this weekend) I'll make the body pane show actual

Re: What to do when outline's text is not visible in tree pane?

Example tooltips can be found in nav_qt.py (plugin) and in LeoPy.leo somewhere around the LeoTabbedTopLevel code, if I recall correctly. Bolting those examples onto headlines is another matter. I spent a lot of time trying things and then "git stash" to restore functioning code. Chris On

Re: Question about running / driving leo 'headless' to integrate it in my own GUI

Impressive progress. This is a pretty exciting development. While many "viewers" have been demonstrated this is one of the first "Leo in an editor" type demonstrations I've seen. Nice work. I look forward to seeing where this goes. On Thursday, August 29, 2019 at 12:09:35 AM UTC-4, Robert