It's been a while since I looked, and maybe things are configurable, but I remember not being impressed by what pylint told me was 'correct' indentation of split lines, on more than one occasion...
On Saturday, September 25, 2021 at 11:37:27 AM UTC+1 Edward K. Ream wrote: > Here are my plans for the next few days, before leaving on vacation > Wednesday, Sept. 29. > > *Complete the mass cleaning of Leo's sources* > > This must be done now, early in the next release cycle. The code cleaning > is being driven by enabling pylint's "format" checkers, which check for > long lines, bad indentation, etc. > > All of Leo's *core *files also pass with the multiple-statements checker > enabled. After a bit of dithering, I've decided to clean *all* of Leo's > files with the multiple-statements checker enabled. There are several > reasons for this: > > - Useful for coverage testing. > - Simulates what black would do. > Leo's own "beautify" command does not split or join lines by default. > - I've grown to dislike cramming two statements on a line. > > I'll likely finish this code cleaning in one or two days. This *will *be > the end of code munging! > > > *Start using leoInteg* > > I shall be using vs-code for at least a few minutes every day. I expect it > will be several weeks before I am truly comfortable with vs code. > > The picture I have is of gently pushing on a seemingly immovable wall. > After a week or two it will suddenly tip over :-) > > I'll start by customizing key bindings, syntax coloring and other parts of > the look and feel. Along the way I'll report any bugs I find to Félix. > > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/74fee243-ffc4-4198-bf72-60241a5385b9n%40googlegroups.com.
