On Tuesday, July 22, 2014 7:42:17 AM UTC-5, Edward K. Ream wrote: > > On Mon, Jul 21, 2014 at 9:52 AM, 'Terry Brown' via leo-editor > <[email protected]> wrote: > > > Given the almost unlimited number of "@auto" formats people might want > > (I'd like R and coffeescript, and LaTeX), I think we're going to need > > some kind of module interface... > > Good idea. It shouldn't be too hard to do.
Recent revs have completed the project, except for the markdown importer ;-) I spent most of today getting unit tests for .rst files and @auto-rst to work. Previously, the unit tests just used a plain-text importer, which defeats their entire purpose. I did add yet another hack to the perfect-import comparison code: the code "canonicalizes" rST over/under lines so as to ignore differences in the length of such lines. I think this is a good compromise: it ensures that important checks for rST are made without complaining about non-essential differences. I'll leave the old code (enabled by the new_importers switch) in for a few more days, but I see no reason not to use the importers in leo/plugins/importers. In fact, I think it would be reasonable to define the all-import BaseScanner class in that directory as well. Edward P.S. Recent code has simplified both the signature and the code for g.importFromPath. This was important: leo.modes.python must be different from leo.plugins.importers.python! There are only a few calls to this function in Leo's core, and none in any file in leo/plugins, but you should be aware of the change. EKR -- 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.
