On Fri, Oct 21, 2011 at 5:02 AM, IaMaPlAyEr <[email protected]> wrote: > thanks a lot! > I think, maybe this tip should be showed in Leo's doc.
:-) Actually, this would not be a good idea. Instead, Leo should work so well enough so that such documentation is not necessary. Leo's core developers know that whatever simplicity Leo appears to have is the result of a lot of behind-the-scenes effort. In this present situation, there are three or four parts of Leo that must work together to create the *illusion* that Leo "understands" various languages: 1. Leo's colorizer. 2. Leo's read/write code for external files. 3. Leo's importers. 4. Tables in leoApp.py. The reason you were confused is that only Leo's colorizer understood matlab. At minimum, there should be entries in leoApp.py for all languages supported by Leo's colorizer. This will ensure that Leo's read/write code can handle all such languages. The tables won't directly help Leo's import code, but that's not such a big deal: the importers already handle "unknown" languages well enough. I've just created a bug report, https://bugs.launchpad.net/leo-editor/+bug/879338, that says that all languages known to the colorizer should have entries in the tables in leoApp.py. 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.
