On Wednesday, March 18, 2015 at 2:15:14 AM UTC-7, Edward K. Ream wrote: > Eureka! This is a major breakthrough relating to bug 158. >> > > I have just fixed several bugs in fc.createSaxVnode. See the comments at > the end of https://github.com/leo-editor/leo-editor/issues/158 > > I could not have found the problems without your report. Many thanks for > taking the time to report the traceback. > > Edward >
Very glad I could help. Does this mean we can open the python.leo file soon? Suggestion: Unless you're about to update the sourceforge version very soon, might I suggest that you put a note on the 'Programming' documentation page that you need the github version to use @clean. However, I am glad that this forced me to go through the initial pain of setting up YAT (yet another tool), so that I could check out this new feature. Works very nicely, I must say. Almost like magic, or quantum entanglement. ;-) YAS (yet another suggestion): This may be an onerous amount of work, but seems like it could be automated: add a revision page to the documentation. It would be a quick way to be alerted to any new or changed features. You could also include a version tag, like 5.1 on the @clean revision. One last nit: The Home page shows 'Leo 5.0' in the top border. -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
