On Mon, Jun 8, 2009 at 5:00 PM, James A. Donald <[email protected]> wrote:
> > On Mon, Jun 8, 2009 at 12:57 PM, Ville M. Vainio <[email protected]> > wrote: > > > This makes me slightly > > > nervous, since I never commit that file (or anything apart from .py > > > files in the first place), and I'm afraid sometimes valuable code in > > > .py file could be thrown away because code in .txt file will take > > > precedence. > > Edward K. Ream wrote: > > That's highly unlikely to happen, because qtNotes.txt will likely be in > > synch with all the .py files when you commit. The only thing to avoid > would > > be to make external changes in qtNotes.txt rather than the "primary" > files. > > You can do this sort of thing, because you are mindful of the internals, > but it is behavior that is dangerous and difficult for naive users - or > even highly sophisticated developers such as Ville M. Vaino. The rule is simple: put files containing @all (or cross-file clones) before all the files that "own" the cross-file clones. > Open source projects have a chronic and infamous tendency to drift away > from user friendliness, I wouldn't put it this way. The drift is towards more and more features. Some may be dubious, but the vast majority are there for a good reason and add significantly to Leo. If this isn't user-friendliness, what is? True, there is a lot to learn to become an expert, but newbies don't have to know any of the new stuff. and the out of dateness of the documentation, > and the non obviousness what is safe and unsafe usage, represents such a > drift. The constraint I discuss above was never documented. It's a hole, not any kind of drift. Please file a doc bug. Edward --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
