Re: Leo's new beautifier: progress report

On Thu, Feb 13, 2020 at 4:02 AM Edward K. Ream wrote: > ...it should be pretty safe to try out the new beautify-files command. There is a problem with @doc and @ sections. Leo uses a too-clever-by-half convention for determining whether blank lines in such sections are "real". At present,

Re: Leo's new beautifier: progress report

On Wednesday, February 12, 2020 at 6:23:45 AM UTC-6, Edward K. Ream wrote: As of rev f8fc59 it should be pretty safe to try out the new beautify-files > command. Again, make sure you have backups of any to-be-beautified file. > Still true. I have beautified all of Leo's files in the fstrings

Re: Leo's new beautifier: progress report

On Tuesday, February 11, 2020 at 7:02:02 AM UTC-6, Edward K. Ream wrote: [Monday] the beautify-files command passed a major milestone: all of Leo's > core files compile without syntax errors after being beautified :-) > As of rev f8fc59 it should be pretty safe to try out the new beautify-files

Re: Leo's new beautifier: progress report

On Tue, Feb 11, 2020 at 7:02 AM Edward K. Ream wrote: Yesterday the beautify-files command passed a major milestone: all of Leo's > core files compile without syntax errors after being beautified :-) > That's no longer true, if it ever was. I'll let you know when I can recommend using

Leo's new beautifier: progress report

Leo's beautify-files command now uses the Orange class in leoAst.py. This class is a proof of concept for #1440 , unify the ast and token worlds. I've been working on this project for almost four months. It is nearing completion. Further