On Jul 7, 1:15 am, "Edward K. Ream" <[email protected]> wrote:
> The discussion about deprecating @file is an entirely different matter. > People have been using @file for 10+ years without significant problems. > > We'll get rid of @file nodes completely in the Leo 4.7 release cycle, but > it's too late to do anything about this in Leo 4.6. > > For now, if you are concerned about @file you can simply convert your @file > nodes to @thin nodes. I've got literally dozens of leo files sitting all over the place. Many of them, especially from years ago, have lots of @file nodes. The thought of a future Leo version failing to load these files does scare me somewhat. IMHO, it would be profoundly unwise to release any future versions of Leo which fail to read @file nodes. It would be fine to read @file nodes and stick up a dialog asking whether the user wants them converted to @nosent or @thin nodes. But to just shut the door on backward compatibility is not something I would be overjoyed about. Cheers David --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
